You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are implements for bit slice index in java and go. Do we need in C/C++?
I think implementing Bit-sliced index for CRoaring include these tasks:
support mutable Bit-sliced index in C
support RangeBitmap in C
A range Index demo for postgres using RangeBitmap in C
A mutable bit-sliced index demo for postgres using bit-sliced index in C
A range index demo for Apache Parequet file-format in C/C++
A mutable bit-sliced index demo for Apache Parequet file-format using Bit-sliced index in C
@lemire we've implemented mutable Bit-sliced index in C and using it for postgres. Due to there are two implements for bit-sliced index, (BSI and RangeBitmap), one is mutable but the performance is poor, the other is immutable ,but the performance is great. Could we make a decision or re-design it ?
@Smallhi : I alos have this use case , any idea when would we be able to merge this implementation.
Also i have a noob question : Why is bit sliced index dependent on Rangebitmap implementation ? What exactly is the difference between range index and bit slice index ?
There are implements for bit slice index in java and go. Do we need in C/C++?
I think implementing Bit-sliced index for CRoaring include these tasks:
@lemire we've implemented mutable Bit-sliced index in C and using it for postgres. Due to there are two implements for bit-sliced index, (BSI and RangeBitmap), one is mutable but the performance is poor, the other is immutable ,but the performance is great. Could we make a decision or re-design it ?
cc @ richardstartin
refer to :
The text was updated successfully, but these errors were encountered: