ESQL: Don't accidentally add flattened subfields#154999
Open
kkharbas wants to merge 1 commit into
Open
Conversation
We were accidentally adding flattened sub fields in queries like: ``` FROM idx_date, idx_flat_date | STATS c = COUNT(metadata.time) ``` In `idx_date` the `metadata.time` field is mapped as `date`. In `idx_flat_date` the `metadata` field is mapped as `flattened`. Without this fix we see the `date` as a real, partially mapped field. So we proceed to process it. On the data node we see the `flattened` sub field and load it like a `keyword` field. Which confuses everything! Because we're expecting a `date` field. Closes elastic#154011 Closes elastic#154484
kkharbas
added
>bug
Team:Analytics
elasticsearchmachine
added
the
serverless-linked
Collaborator
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
dnhatn
approved these changes
Jul 24, 2026
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
4 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.
Summary
Cherry-pick of #154508 onto
patch/serverless-fix.From original PR:
We were accidentally adding flattened sub fields in queries like:
In
idx_datethemetadata.timefield is mapped asdate. Inidx_flat_datethemetadatafield is mapped asflattened.Without this fix we see the
dateas a real, partially mapped field. So we proceed to process it. On the data node we see theflattenedsub field and load it like akeywordfield. Which confuses everything! Because we're expecting adatefield.Closes #154011
Closes #154484
Closes #154743