Some queries do not respect the index.query.parse.allow_unmapped_fields index setting

[Mikep86]

Elasticsearch Version

8.15

Installed Plugins

No response

Java Version

bundled

OS Version

N/A

Problem Description

Some queries do not respect the index.query.parse.allow_unmapped_fields index setting, resulting in them throwing an exception when they should instead return no results. This issue is intended to track all the queries that should be updated:

• KnnVectorQueryBuilder (tracked independently by KnnVectorQueryBuilder does not respect allowUnmappedFields #106846)
• exists query for semantic_text fields (see here)
• nested query

Steps to Reproduce

N/A

Logs (if relevant)

No response

[elasticsearchmachine]

Pinging @elastic/es-search (Team:Search)

[benwtrent]

This is owned by the @elastic/es-search-relevance team.

[benwtrent]

I went through the queries and the only three I could find that do not respect this index setting are:

PercolatorQueryBuilder

WeightedTokensQueryBuilder

SparseVectorQueryBuilder

[elasticsearchmachine]

Pinging @elastic/es-search-relevance (Team:Search Relevance)

[Mikep86]

The nested query also does not respect this setting. Instead, it gets the value from the user-provided "ignore_unmapped" field at query time.