Respect include/exclude patterns when applying exclude_vectors
#135444
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change ensures that the `_source` `include` and `exclude` patterns are applied as exceptions when `exclude_vectors` is enabled.
Previously, `exclude_vectors` was enforced independently of any explicitly defined `include` or `exclude` rules.
With this update, queries like:
```json
{
"_source": {
"exclude_vectors": true,
"includes": ["my_vector_field"]
}
}
```
will correctly include my_vector_field, overriding the exclude_vectors parameter.
jimczi
added
>non-issue
:SearchOrg/Relevance
elasticsearchmachine
added
the
Team:Search - Relevance
|
Pinging @elastic/search-relevance (Team:Search - Relevance) |
kderusso
approved these changes
Sep 25, 2025
...RestTest/resources/rest-api-spec/test/search.vectors/250_source_synthetic_sparse_vectors.yml
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change ensures that the
_sourceincludeandexcludepatterns are applied as exceptions whenexclude_vectorsis enabled.Previously,
exclude_vectorswas enforced independently of any explicitly definedincludeorexcluderules.With this update, queries like:
{ "_source": { "exclude_vectors": true, "includes": ["my_vector_field"] } }will correctly include my_vector_field, overriding the exclude_vectors parameter.