-
Notifications
You must be signed in to change notification settings - Fork 25k
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
[Transform] Fix failure when resolving indices from CCS #91622
Conversation
Hi @hendrikmuhs, I've created a changelog YAML for you. |
Pinging @elastic/ml-core (Team:ML) |
@elasticmachine update branch please |
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.
Am I right that every new test is checking the case of the same index name on both local and remote clusters?
I think it would be nice if one of them tested the case of the same index name on multiple remote clusters but no duplicate on the local cluster. Maybe a unit test for this would be the easiest.
I added a unit test for 3 remotes with same name indices |
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.
LGTM
properly prefix remote indices in checkpoints, fixes a failure when more than 1 cluster is used and index names clash relates elastic#80984 fixes elastic#91550
properly prefix remote indices in checkpoints, fixes a failure when more than 1 cluster is used and index names clash relates elastic#80984 fixes elastic#91550
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.
LGTM
properly prefix remote indices in checkpoints, fixes a failure when more than 1 cluster is used and index names clash
relates #80984
fixes #91550