[9.3] Fix metadata fields being nullified/loaded by unmapped_fields setting (#143155)#143373
Merged
elasticsearchmachine merged 2 commits intoelastic:9.3from Mar 2, 2026
Merged
Conversation
…elastic#143155) Metadata fields (_score, _id, _index, etc.) were incorrectly treated as unmapped fields when SET unmapped_fields="nullify" or "load" was used. This silently returned NULL instead of producing a proper error guiding the user to add METADATA to the FROM clause. Closes elastic#141907 (cherry picked from commit e76c5c1) # Conflicts: # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/analysis/rules/ResolveUnmapped.java
13 tasks
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
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 will backport the following commits from
mainto9.3: