-
Notifications
You must be signed in to change notification settings - Fork 125
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
[BUG] Retreive knn_vector
value raising an error. What's the alternative?
#412
Comments
@igaloly You can use
|
@VijayanB When performing this query, as you suggested, it raises the error: Query:
Also, Is it slow as |
@igaloly doc values are faster if you are loading few fields from documents instead of whole document. Let me try to reproduce this issue and will get back to you soon. |
@igaloly I am able to reproduce this issue and figured out that KNNScriptDocValue is only accessible inside script_score context at this moment. We will work on including additional context to make it accessible. |
@VijayanB Sounds good. |
@igaloly We are targeting for OpenSearch 2.0.1 ( OpenSource) release. Will confirm in few days on when will this be available for managed OpenSearch users. |
Hi @VijayanB |
@igaloly Sorry for late response. We released this feature in OpenSearch 2.0.1 ( Open source). Unfortunately, i don't have any information on when will this be available for managed users at this moment. |
@igaloly As of today managed service is couple of months behind the OpenSearch version. Stay tuned to managed service release page |
closing this thread. Feel free to reopen if you see issues. |
What is the bug?
When I try to retrieve a value from a
knn_vector
, I get this error:knn vector does not support this operation
.I do not want to use
_source
to get the vector, because it's slow.What are my options to save vector with the ability to retrieve it values?
Mapping:
Query:
How can one reproduce the bug?
knn_field
What is the expected behavior?
To get the value of the specific index
What is your host/environment?
The text was updated successfully, but these errors were encountered: