Skip to content
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

[QUESTION]: Does pymilvus support float16 and/or bfloat16 embeddings? #2546

Open
1 task done
BBC-Esq opened this issue Jan 6, 2025 · 3 comments
Open
1 task done
Labels
kind/question A question to answer

Comments

@BBC-Esq
Copy link

BBC-Esq commented Jan 6, 2025

Is there an existing issue for this?

  • I have searched the existing issues

What is your question?

Does pymilvus support float16 and/or bfloat16 embeddings? I am not referring to the "dtype" that an embedding model is being run with but rather the actual embeddings that are returned? For example, I know that tiledb, which I currently use, does not:

https://docs.tiledb.com/spark/supported-datatypes

Anything else?

No response

@BBC-Esq BBC-Esq added the kind/question A question to answer label Jan 6, 2025
@XuanYang-cn
Copy link
Contributor

@BBC-Esq Yes, Milvus and PyMilvus supports bf16 and fp16 embeddings

Ref to PyMilvus example:
https://github.com/milvus-io/pymilvus/blob/master/examples/datatypes/float16_example.py https://github.com/milvus-io/pymilvus/blob/master/examples/datatypes/bfloat16_example.py

Ref to Milvus doc:
Look for Supported data types: https://milvus.io/docs/schema.md

@BBC-Esq
Copy link
Author

BBC-Esq commented Jan 7, 2025

Perfect, thank you. And if I switch my program from tiledb to you guys, what other differences are there?

@XuanYang-cn
Copy link
Contributor

Sorry that I'm not familiar with tiledb, feel free to reach us when anything goes wrong during the switch, we're happy to offer helps on specific problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question A question to answer
Projects
None yet
Development

No branches or pull requests

2 participants