milvus
milvus copied to clipboard
[Bug]: slice size is not set for scalar index
Is there an existing issue for this?
- [X] I have searched the existing issues
Environment
- Milvus version:
- Deployment mode(standalone or cluster):
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
Current Behavior
Now, Milvus supports to build index for scalar field, for example, you can create marisa trie index for string field to save memory. But now Milvus didn't set slice size for these scalar index, so if the marisa trie is very large then the index file may be very also large. Milvus will store these index files into S3/MinIO and they recommend users not to store large files.
Expected Behavior
Slice size should be set for scalar index by default.
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
/unassign @yanliang567 /assign
/assign @xige-16