Re: Can I use CRoaring library in Git?
- From
Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
- Date
- Jul 18, 2022, 08:57 UTC
- Message-ID
- <CAPOJW5w+6jaHJe8FBVzjAfRBATYuV=+uv4HeA_fpRKFbRtKXcw@mail.gmail.com>
- In-Reply-To
- <YtSMVcc59LP1j+Ys@nand.local>
On Mon, Jul 18, 2022 at 3:55 AM Taylor Blau <me@ttaylorr.com> wrote:
Show 9 quoted lines
> > Assuming that we can clear the licensing issues (or we can write our > > own implementation from spec), how would the transition plan look > > like? Does our bitmap format carry enough metadata to allow > > existing clients who never saw anything but ewah bitmaps to say "ah, > > this bitmap file uses encoding I do not understand" and gracefully > > fall back to not using the bitmap? > > Yes, the version field alone does this, since the existing readers know > to ignore a bitmap whose version they do not understand.
Yeah, the version field itself is enough to do this.
> I assume that Abhradeep will want to pursue some format redesign as part > of the transition, though, at least to see if changing the format beyond > a version bump and new compression scheme is worthwhile.
I haven't thought much about it until now. As far as I think we don't need Xor Flag anymore. My primary goal is to implement Roaring Bitmap as soon as possible and perform performance testing. If the performance tests give good results, I will think about reformatting. As far as it seems most will stay the same.
Thanks :)