描述
Is there an existing issue for this?
- I have searched the existing issues
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?