-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Null handling bitmap performance #5569
Comments
This issue has been marked as stale due to 280 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions. |
I believe this is still relevant. |
This issue is no longer marked as stale. |
@gianm any idea why a get with an offset is more expensive than walking iterator ? |
@b-slim I'm not familiar with their implementation enough to know, but I could speculate. Perhaps the compressed bitmap iterators cache some information that needs to be re-computed if you are calling |
Fixed by #8822. |
I noticed that the null bitmap checks from #5278 are usually implemented like:
From what I recall,
get
on compressed bitmaps can be quite slow compared to walking an iterator.The text was updated successfully, but these errors were encountered: