-
Notifications
You must be signed in to change notification settings - Fork 232
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
Does there exist an efficient approach to convert between 64bit roaring and 32bit roaring? #252
Comments
I do not understand this issue. Can you provide a sample Go code that you are using? |
This code snippet is used to extract ids from source roaring bitmap(eg 64bit roaring), and then insert to target roaring bitmap after the type conversion (eg 32bit roaring). The overhead is pretty high, any suggestions to make this precedure accelerated? |
What is a 64-bit roaring bitmap? There is no such thing in the library right now. |
Oh, sorry, |
Right. So the question is how to go from Pilosa to the roaring implementation in this repo, here, is that correct? |
Using the WIP 64bit solution of this repo, could the conversion between 32bit and 64bit roaring have a faster approach? |
Yeah... but the WIP is a WIP. We need help with it to make sure it meets people’s needs. Could you help? |
We've met a situation that the conversion between 64bit roaring and 32bit roaring needs to be computed very fast. Currently, we can only use a naive solution that during iterating one bitmap while inserting into the other at the same time, which is pretty time consuming given a high bitmap cardinality. Is it possible to provide an efficient approach such that the conversion could be performed internally without decompression and compression one by one?
The text was updated successfully, but these errors were encountered: