- Notifications
You must be signed in to change notification settings - Fork 25.5k
Handle the indices pattern ["*", "-*"]
when grouping indices by cluster name #128610
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
pawankartik-elastic merged 7 commits into elastic:main from pawankartik-elastic:pkar/detect-no-indices-aliases-pattern Jun 3, 2025
Merged
Changes from all commits
Commits
Show all changes
7 commits Select commit Hold shift + click to select a range
b3c3f9d
Handle the indices pattern `["*", "-*"]` when grouping indices by clu…
pawankartik-elastic cd388ae
Apply review comments
pawankartik-elastic d29a9c3
Drop redundant code comment
pawankartik-elastic 7a76fca
Merge branch 'main' into pkar/detect-no-indices-aliases-pattern
pawankartik-elastic bac027a
Update docs/changelog/128610.yaml
pawankartik-elastic 00020a3
Apply review comments
pawankartik-elastic 07449bb
Merge branch 'main' into pkar/detect-no-indices-aliases-pattern
pawankartik-elastic File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
pr: 128610 | ||
summary: "Handle the indices pattern `[\"*\", \"-*\"]` when grouping indices by cluster\ | ||
\ name" | ||
area: CCS | ||
type: bug | ||
issues: [] |
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perhaps add a comment here, that explains the semantics of returnLocalAll and where it's used set to false.
I wonder if in the longer run, we should consider making resolve cluster go through a specific method that resolves clusters instead of indices, and remove this flag that makes things a little difficult to read. What do you think? Do we ever consume the indices names (values in the map) or only the cluster aliases (keys in the map)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although we don't return the indices names directly, the
_resolve/cluster
call's response has a keymatching_indices
that tells if the specified cluster has the specified index.