Update migrate_5_0.asciidoc

Updated breaking changes to state that upgraded indices still need to be reindexed,
and to mention the migration plugin
This commit is contained in:
Clinton Gormley 2016-06-23 13:10:50 +02:00 committed by GitHub
parent 33313df0a2
commit 5a08e36f9c

View File

@ -4,6 +4,14 @@
This section discusses the changes that you need to be aware of when migrating
your application to Elasticsearch 5.0.
[float]
[[migration-plugin]]
=== Migration Plugin
The https://github.com/elastic/elasticsearch-migration/blob/2.x/README.asciidoc[`elasticsearch-migration` plugin]
(compatible with Elasticsearch 2.3.0 and above) will help you to find issues
that need to be addressed when upgrading to Elasticsearch 5.0.
[float]
=== Indices created before 5.0
@ -16,9 +24,10 @@ version of Elasticsearch before 2.0.
=========================================
Indices created in Elasticsearch 1.x or before will need to be reindexed with
Elasticsearch 2.x in order to be readable by Elasticsearch 5.x. The easiest
way to do this is to upgrade to Elasticsearch 2.3 or later and to use the
`reindex` API.
Elasticsearch 2.x in order to be readable by Elasticsearch 5.x. It is not
sufficient to use the <<indices-upgrade,`upgrade`>> API. The easiest
way to reindex old indices is to upgrade to Elasticsearch 2.3 or later and to use the
`reindex` API, or the reindex UI provided by the <<migration-plugin,Migration Plugin>>.
=========================================