Create index mapping from FieldCaps response #137962
Open
+135
−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
idegtiarenko
added
>non-issue
Team:Analytics
idegtiarenko
commented
Nov 12, 2025
| hasEntry(REMOTE_CLUSTER_2, resolvedIndexExpression("index-*", "index-3")) | ||
| ) | ||
| ); | ||
| } |
Contributor
Author
There was a problem hiding this comment.
I believe we do not support exclusions yet
Collaborator
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
luigidellaquila
approved these changes
Nov 13, 2025
elasticsearchmachine
added
the
serverless-linked
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 adds a component that parses FieldCaps response and creates cluster -> (expression, resolved) mapping.
This information is going to be supplied to query execution engine once #137879 is merged.