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
Implement MlConfigIndexMappingsFullClusterRestartIT test which verifies that .ml-config index mappings are properly updated during cluster upgrade #44341
Conversation
Pinging @elastic/ml-core |
run elasticsearch-ci/2 |
run elasticsearch-ci/bwc |
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.
On your backport, you may have to do some version restrictions (or add handlers for versions before 7.2.0).
…es that .ml-config index mappings are properly updated between versions 6 and 7.
eb500c9
to
cfb1b7c
Compare
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
...src/test/java/org/elasticsearch/xpack/restart/MlConfigIndexMappingsFullClusterRestartIT.java
Outdated
Show resolved
Hide resolved
…es that .ml-config index mappings are properly updated during cluster upgrade (elastic#44341)
…es that .ml-config index mappings are properly updated during cluster upgrade (elastic#44341)
…es that .ml-config index mappings are properly updated during cluster upgrade (elastic#44341)
…es that .ml-config index mappings are properly updated during cluster upgrade (elastic#44341)
This PR adds a test which verifies that .ml-config index mappings are properly updated during cluster upgrade from version 7 to 8.
It verifies the existence of data frame analytics mappings which were introduced in 7.3.
Data frame analytics mappings may show up either in:
or
Related to #44263