-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Feature]: Support Blob datatype #27578
Comments
Hi am a current student and want to start my first PR as an open-source contributor, can you assign this to me? |
Sure my man. /assign @MZHL111 let me know what's your plan and I would be glad to help |
@xiaofan-luan: GitHub didn't allow me to assign the following users: MZHL111. Note that only milvus-io members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@xiaofan-luan Thank you :). Do you know which module or file I should start with to get familiar with the code base? |
To add new data type, you will have to
|
@xiaofan-luan |
Is there an existing issue for this?
Is your feature request related to a problem? Please describe.
User some times want to store large blobs into Milvus, for example, store a image or a pdf into milvus and retrieve.
To support store blob, milvus don't store data itself but only store the object storage path.
The blob is stored to S3 on proxy, with the correct path, and the actual field on milvus is a string which contains the S3 path.
User can not query or filter on Blob, but blob can be specified as the output field.
On search/query, if blob is specified as output field, proxy is responsible for retrieve the data out and response to user.
Currently, the blob has a limitation of 16M.
Describe the solution you'd like.
No response
Describe an alternate solution.
No response
Anything else? (Additional Context)
To be discussed:
if user ask for large topk, return all the blobs to client may break the grpc size limit.
How to handle it? should we return all the file list to client and retrieve the real blob from client by another rpc?
The text was updated successfully, but these errors were encountered: