Allow TermsEnum to express a preference for seekExact to FrozenBufferedUpdates #15636
+60
−5
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
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.
For Terms implementations that have an approximate membership filter, the current scheme of repeated
seekCeil() calls when evaluating update/deletion terms can cause the membership filter to be skipped as
we must provide the term after the target on a miss. Allow TermsEnum to express a preference for seekExact()
so that approximate membership filters still work in this case.
Implement
preferSeekExact()inBloomFilteringPostingsFormatwhere there is obvious benefit.