You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today the content for the text and images for mutimodal semantic search is provided directly with the request in form of base64 encoded string. This requires additional pre-processing of data and not be optimal is some scenarios when for instance data is already available in some other system. Another problem is storage space, in OpenSearch this binary content will be stored as part of the index.
What solution would you like?
Allow URLs for fields, something around these lines:
Alternative is available now, user needs to download content from the URL and do base64 encoding
Do you have any additional context?
There can be concerns around security as system will be pulling from remote URLs. Most probably the syntax of existing requests will change to support url type
The text was updated successfully, but these errors were encountered:
martin-gaievski
changed the title
[FEATURE] Pulling content for neural search from user provided URL
[FEATURE] Pulling fields content for neural search from user provided URL
Oct 25, 2023
This idea may not be ideal for managed systems, mainly because URL is provided by user and that may be not secure and/or can affect system stability. At some degree the overhead with storage can be solved by not storing field source in the index.
Is your feature request related to a problem?
Today the content for the text and images for mutimodal semantic search is provided directly with the request in form of base64 encoded string. This requires additional pre-processing of data and not be optimal is some scenarios when for instance data is already available in some other system. Another problem is storage space, in OpenSearch this binary content will be stored as part of the index.
What solution would you like?
Allow URLs for fields, something around these lines:
What alternatives have you considered?
Alternative is available now, user needs to download content from the URL and do base64 encoding
Do you have any additional context?
There can be concerns around security as system will be pulling from remote URLs. Most probably the syntax of existing requests will change to support url type
The text was updated successfully, but these errors were encountered: