Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose
Enable row-level bitmap file-index pushdown for data evolution merged
file groups.
Previously, bitmap indexes could only skip an entire merged group. A
non-empty bitmap could not filter individual rows because applying it to
only one field reader would break positional alignment.
This change builds a shared bitmap selection from eligible file-index
results and applies it to every aligned reader in the merged group. The
optimization is limited to normal data files with identical row-id
ranges. Blob files, vector-store files, and non-bitmap index results
continue to use the conservative fallback path.
Tests
data evolution merged group.
field files.
bitmap selection returns live matching rows while deleted matching
groups are skipped.