Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This crate vs tantivy-bitpacker #44

Open
ccleve opened this issue Feb 15, 2023 · 2 comments
Open

This crate vs tantivy-bitpacker #44

ccleve opened this issue Feb 15, 2023 · 2 comments

Comments

@ccleve
Copy link

ccleve commented Feb 15, 2023

I noticed that there is a separate crate under the Tantivy project that also does bitpacking. So far as I can tell, the other crate does 64 bit compression and does not use SIMD, and the Tantivy project uses both crates. Is this correct?

Can I ask about the future of this crate? Will you be consolidating the two? What's the plan?

Also, it appears that the master branch is at version 0.8.3, but crates.io has 0.8.4. Is there some other repo somewhere I've missed?

@PSeitz
Copy link
Contributor

PSeitz commented Feb 16, 2023

I noticed that there is a separate crate under the Tantivy project that also does bitpacking. So far as I can tell, the other crate does 64 bit compression and does not use SIMD, and the Tantivy project uses both crates. Is this correct?

That's correct

Can I ask about the future of this crate? Will you be consolidating the two? What's the plan?

Currently there's no plan to merge the two, they serve different purposes. big blocks of u32 used in the posting list vs various length u64

Also, it appears that the master branch is at version 0.8.3, but crates.io has 0.8.4. Is there some other repo somewhere I've missed?

Probably some locally uncommitted data? @fulmicoton

@fulmicoton
Copy link
Contributor

Also, it appears that the master branch is at version 0.8.3, but crates.io has 0.8.4. Is there some other repo somewhere > I've missed?

That's actually a mystery. I could not spot what branch was published. I must have messed up and Cargo pushed over the commit bumping the version.
I did cargo download the crate to check if we are facing something more malicious ... but the diff does not present anything suspicious..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants