-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Deprecate Migration Assistance and Upgrade APIs #40072
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
Changes from all commits
2b6db5e
d25ec37
40ad9e4
8b6d3de
03bd069
52f2191
f806fef
d409eba
2662145
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,8 +6,14 @@ | |
<titleabbrev>Migration upgrade</titleabbrev> | ||
++++ | ||
|
||
The Migration Upgrade API performs the upgrade of internal indices to make them | ||
compatible with the next major version. | ||
IMPORTANT: To prepare a cluster for an upgrade to Elasticsearch version 7, use | ||
the {kibana-ref}/upgrade-assistant.html[{kib} Upgrade Assistant] or | ||
<<reindex-upgrade,reindex manually>> before upgrading. | ||
|
||
deprecated[6.7, Use the {kibana-ref}/upgrade-assistant.html[{kib} Upgrade | ||
Assistant] or <<reindex-upgrade,reindex manually>> before upgrading.] The | ||
migration upgrade API performs the upgrade of internal indices to make them | ||
compatible with version 6 of Elasticsearch. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If someone uses this API in 6.7 will it work correctly ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I've made a tweak to this to make sure the behavior aligns, but as of this PR, if used in 6.7, the Upgrade API will only upgrade indices that need to be upgraded from their 5.x format (i.e. they were not upgraded before upgrading the cluster). Otherwise, it will just say that the index needs to be reindexed. That is, if the |
||
|
||
[float] | ||
==== Request | ||
|
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.
If someone uses this API in 6.7, will it return correct information ?
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.
I've made a tweak to this to make sure the behavior aligns, but as of this PR, if used in 6.7, this API will correctly identify which indices need to be reindexed, including internal indices. It will only say that indices need to be "upgraded" if they were not properly upgraded before upgrading the cluster to 6 and need to be fixed using the Migration Upgrade API.