feat: add filter_deleted
option to avoid removing deletion markers
#3707
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
This PR adds an
filter_deleted
option toMergeReader
so that it will not remove deletion markers (or tombstones) during merging.filter_deleted
is different fromdedup
in that:dedup
is set to false, thenfilter_deleted
will always be false since deletion markers are not expected to present.dedup
is set to true, thenfilter_deleted
decides whether deletion markers should be removed.This PR is the predecessor work of #3702.
Checklist