RoaringBitmap / RoaringBitmap/RoaringBitmap
efficient way to do nextOff(long fromPosition) with Roaring64Bitmap
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.9k
- Forks
- 592
- Avg merge
- 5d 21h
- Merged PRs (30d)
- 2
Description
Is your feature request related to a problem? Please describe.
Whats the recommended way to find nextOff(long fromPosition) to see whats the bit which is turned off from a given position ? This is useful to compress contiguous values
Describe the solution you'd like
When determining the contiguous ranges from the first value in the RoaringBitmap it is sometimes needed to find the next bit which is turned off. Any pointers on how this can be accomplished without getting the full entries, or using forEach() to traverse the bitmap and getting the desired value ?
Please note that this is a community-based project. Consider proposing a fix (code, documentation) as a pull request.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Roaring64Bitmap entry point and inspect the existing ways to access entries and traverse with forEach(). Determine whether an efficient nextOff(long fromPosition) operation can be specified without materializing all entries or scanning with forEach(); done means the recommended approach or API is documented and supported by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100