Skip to content
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

Merged
merged 5 commits into from
Nov 18, 2022

Conversation

hendrikmuhs
Copy link

properly prefix remote indices in checkpoints, fixes a failure when more than 1 cluster is used and index names clash

relates #80984
fixes #91550

@elasticsearchmachine elasticsearchmachine added the needs:triage Requires assignment of a team area label label Nov 16, 2022
@hendrikmuhs hendrikmuhs added :ml/Transform Transform auto-backport-and-merge and removed needs:triage Requires assignment of a team area label labels Nov 16, 2022
@elasticsearchmachine elasticsearchmachine added the Team:ML Meta label for the ML team label Nov 16, 2022
@elasticsearchmachine
Copy link
Collaborator

Hi @hendrikmuhs, I've created a changelog YAML for you.

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/ml-core (Team:ML)

@hendrikmuhs
Copy link
Author

@elasticmachine update branch please

@hendrikmuhs hendrikmuhs added v8.5.3 and removed v8.5.2 labels Nov 17, 2022
Copy link
Contributor

@droberts195 droberts195 left a 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.

@hendrikmuhs
Copy link
Author

I added a unit test for 3 remotes with same name indices

Copy link
Contributor

@droberts195 droberts195 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@hendrikmuhs hendrikmuhs merged commit 4c521d0 into elastic:main Nov 18, 2022
hendrikmuhs pushed a commit to hendrikmuhs/elasticsearch that referenced this pull request Nov 18, 2022
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
hendrikmuhs pushed a commit to hendrikmuhs/elasticsearch that referenced this pull request Nov 18, 2022
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
elasticsearchmachine pushed a commit that referenced this pull request Nov 18, 2022
)

properly prefix remote indices in checkpoints, fixes a failure when more than 1 cluster is used and index names clash

relates #80984
fixes #91550
elasticsearchmachine pushed a commit that referenced this pull request Nov 18, 2022
)

properly prefix remote indices in checkpoints, fixes a failure when more than 1 cluster is used and index names clash

relates #80984
fixes #91550
Copy link
Contributor

@przemekwitek przemekwitek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

craigtaverner added a commit to craigtaverner/elasticsearch that referenced this pull request Nov 21, 2022
craigtaverner added a commit that referenced this pull request Nov 21, 2022
* Regenerated release notes for three bug fixes

* #91659
* #91710
* #91622

* Added highlight notes for cartesian centroid and bounds
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Transform] Transform can fail resolving indices from CCS clusters
5 participants