Skip to content

Commit 53cefc1

Browse files
committed
Update the supported versions for archive indices
Fixes #3577
1 parent 4e075f5 commit 53cefc1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

deploy-manage/upgrade/deployment-or-cluster/reading-indices-from-older-elasticsearch-versions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ products:
99

1010
# Reading indices from older {{es}} versions [archive-indices]
1111

12-
{{es}} has full query and write support for indices created in the previous major version. If you have indices created in {{es}} versions 5 or 6, you can use the archive functionality to import them into newer {{es}} versions as well.
12+
{{es}} has full query and write support for indices created in the previous major version. If you have indices created in {{es}} versions 5, 6, or 7, you can use the archive functionality to import them into newer {{es}} versions as well.
1313

1414
The archive functionality provides slower read-only access to older {{es}} data, for compliance or regulatory reasons, the occasional lookback or investigation, or to rehydrate parts of it. Access to the data is expected to be infrequent, and can therefore happen with limited performance and query capabilities.
1515

@@ -50,7 +50,7 @@ Due to `_source` access, the data can also be [reindexed](https://www.elastic.co
5050

5151
## Upgrade older {{es}} clusters [_how_to_upgrade_older_es_clusters]
5252

53-
To upgrade older {{es}} 5 or 6 clusters:
53+
To upgrade older {{es}} 5, 6, or 7 clusters:
5454

5555
1. Take a snapshot of the indices in the old cluster.
5656
2. Delete any indices created before 8.0.0.

0 commit comments

Comments
 (0)