Optimize NextKey / NextPosition in TermIterator with priority-queue for min key/position checks #508
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.
Please do not review yet - I am working on this PR when I get time in between some other core changes, and waiting for the core changes to first get merged into the fulltext branch. After that, I will have this branch updated on latest changes and mark it as ready for review.
In this PR, I optimize NextKey / NextPosition in TermIterator by using a priority queue for efficiently finding the min key and min position when using the key iterator and position iterator