Skip to content

Dynamic pruning with DocValue skipper #14666

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
gf2121 opened this issue May 14, 2025 · 0 comments · May be fixed by #14672
Open

Dynamic pruning with DocValue skipper #14666

gf2121 opened this issue May 14, 2025 · 0 comments · May be fixed by #14672
Labels
type:enhancement

Comments

@gf2121
Copy link
Contributor

gf2121 commented May 14, 2025

Description

We are requiring point tree index to get the dynamic pruning optimization. Can we take advantage of sparse index to do this as well? Several benefits i can think of:

  • Work without point tree index.
  • Save big bitset allocations.
  • Respect maxDocVisited naturally.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Dynamic pruning with DocValueSkipper gf2121/lucene
1 participant
@gf2121