Fix attribute only in full text function not found #137395
Open
+77
−0
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
elasticsearchmachine
added
needs:triage
julian-elastic
added
:Analytics/ES|QL
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
|
Hi @julian-elastic, I've created a changelog YAML for you. |
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.
A verification expection is thrown if there is LOOKUP JOIN with a FULL TEXT FUNCTION on the LOOKUP INDEX. The field from the LOOKUP INDEX is only used in the full text function. There is KEEP that selects some fields, but not the field in question.
The fix involves making sure that all the fields from the JoinOnCondition of the LOOKUP JOIN are collected during resolveFieldNames() to be used for field caps.
Resolves #137396