Skip to content

[7.x] [DOCS] Update version detail in upgrade instructions #221

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
merged 2 commits into from
Feb 25, 2019

Conversation

lcawl
Copy link
Contributor

@lcawl lcawl commented Feb 19, 2019

This PR updates the "important" warning at the top of https://www.elastic.co/guide/en/elastic-stack/7.x/upgrading-elastic-stack.html

Per #219 (comment)

... The "2.x" in that bit should be whatever is two major versions earlier, so for 8.x it should be 6.x and for 7.x it should be 5.x.

@lcawl lcawl added the v7.1.0 label Feb 19, 2019
@lcawl lcawl requested a review from debadair February 19, 2019 19:45
@lcawl lcawl added the v7.0.0 label Feb 19, 2019
@lcawl lcawl requested a review from bleskes February 21, 2019 18:57
@@ -23,8 +23,8 @@ Rolling upgrades are supported when upgrading from Elasticsearch 5.6 and
Elasticsearch 6.0-6.2 to {version}. Upgrading from any
version prior to 5.6 requires a full cluster restart.

IMPORTANT: 2.x indices are not compatible with {version}. You must
remove or reindex them on your 5.n cluster before upgrading to {version}. The internal
IMPORTANT: 5.x indices are not compatible with {version}. You must
Copy link

Choose a reason for hiding this comment

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

should 5.x or older?

@lcawl lcawl merged commit 41d80f9 into elastic:7.x Feb 25, 2019
@lcawl lcawl deleted the upgrade-7x branch February 25, 2019 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants