-
Notifications
You must be signed in to change notification settings - Fork 24.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
KnnVectorQueryBuilder support for allowUnmappedFields #107047
base: main
Are you sure you want to change the base?
KnnVectorQueryBuilder support for allowUnmappedFields #107047
Conversation
Pinging @elastic/es-search (Team:Search) |
I think the change looks good. Gonna get CI to test. Thank you @ghostspiders ! |
buildkite test this please |
buildkite test this please |
@elasticmachine update branch |
buildkite test this please |
There are multiple failures around the yaml tests:
is one example. I am thinking that those tests need to adjusted with a version skip to ensure that they are only ran on older versions where we would fail on a non-existent field directly. |
@benwtrent I passed this yaml tests |
buildkite test this please |
@elasticmachine update branch |
buildkite test this please |
buildkite test this please |
buildkite test this please |
@elasticmachine update branch |
buildkite test this please |
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
KnnVectorQueryBuilder does not respect the index.query.parse.allow_unmapped_fields index setting. update KnnVectorQueryBuilder support for allowUnmappedFields.
#106846