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
Currently, cuVS is using Raft Bitset to do pre-filtering. Only uint32_t data type is supported for Milvus index, but client might have created their bitset using another data type. For example Milvus create their bitset using uint8_t. This changes the way the bits are ordered.
A solution would be to remove the bitset data type template to always use our preferred data type, and accept any bitset by specifying the data type that was used to create it.
The text was updated successfully, but these errors were encountered:
Currently, cuVS is using Raft Bitset to do pre-filtering. Only
uint32_t
data type is supported for Milvus index, but client might have created their bitset using another data type. For example Milvus create their bitset usinguint8_t
. This changes the way the bits are ordered.A solution would be to remove the bitset data type template to always use our preferred data type, and accept any bitset by specifying the data type that was used to create it.
The text was updated successfully, but these errors were encountered: