RoaringBitmap / RoaringBitmap/roaring
Investigate "sroar": Dgraph's Serialized Roaring Bitmaps
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.9k
- Forks
- 262
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 8
Description
Dgraph has made public their "Serialized Roaring Bitmaps" implementation at
https://github.com/dgraph-io/sroar
sroar is a re-written version of Roaring Bitmaps in Go, with the aim to have equality between in-memory representation and on-disk representation. An sroar.Bitmap does not need to be marshalled or unmarshalled, as the underlying represetation is a byte slice. Therefore, it can be written to disk, brought to memory, or shipped over the network immediately.
I would encourage the Roaring community to go have a look.
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
Review Dgraph's sroar implementation at https://github.com/dgraph-io/sroar and assess its serialized Roaring Bitmap approach. The issue names no files or tests and does not define a concrete change, so completion would require documenting whether an actionable adaptation is warranted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100