Skip to content

core: fix pagination and lazily compute OR #1754

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.

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

Merged
merged 1 commit into from
Mar 27, 2025

Conversation

brharrington
Copy link
Contributor

Update RoaringTagIndex implementation to fix pagination of findItems for range and pattern clauses. Before the offset was being ignored for these query clauses. In common usage it often wouldn't be noticed because AND with an equal clause would result in the offset gettng applied via the conjunction.

Also updates range queries and patterns to use a lazy OR operation on the bitmap. In some of our benchmarks this improves the throughput by about 30%.

Update RoaringTagIndex implementation to fix pagination
of findItems for range and pattern clauses. Before the
offset was being ignored for these query clauses. In
common usage it often wouldn't be noticed because AND
with an equal clause would result in the offset gettng
applied via the conjunction.

Also updates range queries and patterns to use a lazy
OR operation on the bitmap. In some of our benchmarks
this improves the throughput by about 30%.
@brharrington brharrington added this to the 1.8.0 milestone Mar 27, 2025
@brharrington brharrington merged commit 5aefc69 into Netflix:main Mar 27, 2025
5 checks passed
@brharrington brharrington deleted the lazy-or branch March 27, 2025 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant