-
Notifications
You must be signed in to change notification settings - Fork 68
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] 2.15 Hybrid Search With query_text and radial vector search producing array out of bounds #973
Comments
@iyoung thank you for informing us about this scenario. I have tried following scenario, it works fine on my side:
I tried multiple search words and different values of |
Same for my query after 2.13 > 2.15 upgrade. Especially this:
Issue happens randomly and it is possible to reproduce only for several minutes/hours. I cannot reproduce it for totally the same query after (probably, index data changes affect this). 2 nodes, 1 primary shard, 1 replica shard, ~600k documents (~13GB), Query is mostly the same as topic starter query but with three subqueries (text search + 2 knn). And also no Any ideas? |
Thank you, I am in contact with the Opensearch managed service team within AWS about this issue and looking to replicate this with a smaller index. The index we're using has around 2m documents in it. Once I have a more concrete way to reproduce this I will update. Thank you for replying. |
@iyoung any update on this issue with reproducing the bug? Thanks |
What is the bug?
Running a hybrid query which contains a min score for the vector side below 0.5 and providing a query_text form lexical search for certain searches (possibly related to number of matches) results in the following response:
How can one reproduce the bug?
This is the structure of query I am using which always throws the exception.
What is the expected behaviour?
Search results returned
What is your host/environment?
AWS managed Opensearch 2.15
Do you have any additional context?
Increasing the radial search threshold by increasing the min score on the vector search to 0.5 to 1 stops this, also by changing the query term or fields included and therefore the matched items also avoids this.
There are numerous exact phrase search terms which cause this issue for us, such as "group hiking" and "cold weather"
In the error logs I get: -
The text was updated successfully, but these errors were encountered: