RoaringBitmap / RoaringBitmap/roaring
External-memory roaring data structure
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 262
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 8
Description
Hello.
I know that FromBuffer/FrozenView methods allow read from MMAP-file.
But how to create such MMAP-file in roaring format: i f my bitmap > RAM? (or if I would like enforce some RAM usage limit)
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 by reading the existing FromBuffer and FrozenView methods and how they consume an MMAP-file. The issue does not name files, tests, or an implementation approach; first determine whether creating a roaring-format file under a RAM limit is supported and where such behavior would belong. Done would require an agreed design and implementation for external-memory creation, with tests covering bitmaps larger than available RAM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100