Looking at the Proto definitions in schema.proto, I see the following types are allowed for scalar fields:

Looking at the Proto definitions in schema.proto, I see the following types are allowed for scalar fields:

After building the vector library in version 2.4.0, we sliced the data and then performed queries later on. We found that querying the same issue sometimes yields different results, and occasionally, the results are not the expected answers. How should we troubleshoot this situation? The collection is standalone, and no operations were performed on it.

When I perform a search with expr and vector, what does Milvus filter first? by expr first, or vector?

I cannot get prefix search to work on a scalar field. I can however get infix search to work which suggests that my field is not properly tokenized.

Are there any settings on how to delete data on disk immediately after drop table on Attu?

I have with 10 million embeddings which are 1536 dims long. I’m fairly confident this means I need less than 128 GB of memory. I’m running Milvus using EKS on AWS and have 2 m6i.4xlarge machines which have 64 GB of memory each, meaning I should have plenty of memory.