Commit 36852ce
prune: update free-space filter when no max-space set
When free-space filter is set without max-space or reserved-space
filter, the behaviour is that if the filter matches some records
then these records would be pruned, but if it doesn't match any
(there are more free space than filter sets already) then the keepBytes
would be left to 0, resulting records to be deleted as if no storage
constraint was set at all.
Signed-off-by: Tonis Tiigi <[email protected]>1 parent 9c8ee9e commit 36852ce
1 file changed
+3
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1092 | 1092 | | |
1093 | 1093 | | |
1094 | 1094 | | |
| 1095 | + | |
| 1096 | + | |
| 1097 | + | |
1095 | 1098 | | |
1096 | 1099 | | |
1097 | 1100 | | |
| |||
0 commit comments