git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Kaartic Sivaraam" <kaartic.sivaraam@gmail.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	git <git@vger.kernel.org>,
	"Derrick Stolee" <derrickstolee@github.com>
Subject: Re: Can I use CRoaring library in Git?
Date: Mon, 18 Jul 2022 14:27:59 +0530	[thread overview]
Message-ID: <CAPOJW5w+6jaHJe8FBVzjAfRBATYuV=+uv4HeA_fpRKFbRtKXcw@mail.gmail.com> (raw)
In-Reply-To: <YtSMVcc59LP1j+Ys@nand.local>

On Mon, Jul 18, 2022 at 3:55 AM Taylor Blau <me@ttaylorr.com> wrote:
> > 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 :)

  reply	other threads:[~2022-07-18  8:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16 13:50 Can I use CRoaring library in Git? Abhradeep Chakraborty
2022-07-16 14:16 ` Ævar Arnfjörð Bjarmason
2022-07-16 16:26   ` Abhradeep Chakraborty
2022-07-17 12:25     ` Kaartic Sivaraam
2022-07-17 22:00       ` Junio C Hamano
2022-07-17 22:25         ` Taylor Blau
2022-07-18  8:57           ` Abhradeep Chakraborty [this message]
2022-07-25 22:11             ` Taylor Blau
2022-07-17 14:43 ` Derrick Stolee
2022-07-18 11:13 ` Jakub Narębski
2022-07-18 11:38   ` Abhradeep Chakraborty
2022-07-18 13:38     ` Ævar Arnfjörð Bjarmason
2022-07-18 11:48 ` Abhradeep Chakraborty
2022-07-18 12:18   ` Derrick Stolee
2022-07-18 13:15     ` Abhradeep Chakraborty
2022-07-18 21:48     ` brian m. carlson
2022-07-25 22:14     ` Taylor Blau
2022-07-25 22:35       ` rsbecker
2022-07-25 23:37         ` Taylor Blau
2022-07-21  4:07 ` Abhradeep Chakraborty
2022-07-21  6:12   ` Junio C Hamano
2022-07-21 12:14     ` Derrick Stolee
2022-07-21 13:51       ` Ævar Arnfjörð Bjarmason
2022-07-21 14:57         ` Abhradeep Chakraborty
2022-07-22 11:07           ` Ævar Arnfjörð Bjarmason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPOJW5w+6jaHJe8FBVzjAfRBATYuV=+uv4HeA_fpRKFbRtKXcw@mail.gmail.com' \
    --to=chakrabortyabhradeep79@gmail.com \
    --cc=avarab@gmail.com \
    --cc=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=me@ttaylorr.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).