Make the Lucene planner optionally convert residual filters into a composite bitmap value plan #3812
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
It passes but needs some assertions commented out about how it passes.
…mposite bitmap value plan. Run that plan to get docid bitsets to and with text matches.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is useful for low cardinality fields that change much more frequently than the actual full text and saves deleting and re-adding a whole document just for those changes. The covering bitmap value index scan is effectively used in place of a
PointValuesinverted index.Basic outline of the execution model. The conversion of bitmap value positions to segment doc ids needs lots of further optimization and moreover fundamentally depends on there being some correlation between them.