honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/docs/reference/migration/migrate_5_0.asciidoc

68 lines
1.9 KiB
Plaintext
Raw Normal View History

Move migrate_3_0 to migrate_5_0
2016-02-29 09:35:48 -05:00
[[breaking-changes-5.0]]
== Breaking changes in 5.0
Remove the scan and count search types. These search types have been deprecated in 2.1 and 2.0 respectively, and will be removed in 3.0.
2015-09-03 09:00:52 -04:00
This section discusses the changes that you need to be aware of when migrating
Move migrate_3_0 to migrate_5_0
2016-02-29 09:35:48 -05:00
your application to Elasticsearch 5.0.
Add upgrader to upgrade old indices to new naming convention
2016-03-14 23:13:06 -04:00
[float]
=== Indices created before 5.0
Elasticsearch 5.0 can read indices created in version 2.0 and above. If any
of your indices were created before 2.0 you will need to upgrade to the
latest 2.x version of Elasticsearch first, in order to upgrade your indices or
to delete the old indices. Elasticsearch will not start in the presence of old
indices. To upgrade 2.x indices, first start a node which have access to all
the data folders and let it upgrade all the indices before starting up rest of
the cluster.
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
[IMPORTANT]
.Reindex indices from Elasticseach 1.x or before
=========================================
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.
=========================================
[float]
=== Also see:
Move migrate_3_0 to migrate_5_0
2016-02-29 09:35:48 -05:00
* <<breaking_50_search_changes>>
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
* <<breaking_50_mapping_changes>>
* <<breaking_50_percolator>>
* <<breaking_50_index_apis>>
* <<breaking_50_settings_changes>>
* <<breaking_50_allocation>>
Move migrate_3_0 to migrate_5_0
2016-02-29 09:35:48 -05:00
* <<breaking_50_rest_api_changes>>
* <<breaking_50_cat_api>>
* <<breaking_50_java_api_changes>>
* <<breaking_50_packaging>>
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
* <<breaking_50_plugins>>
Use `mmapfs` by default. I case any problem was discovered, you can still enable the legacy `default` directory instead. But the plan is to get rid of it in 6.0. Closes #16983
2016-04-08 06:18:02 -04:00
* <<breaking_50_fs>>
Add -XX+AlwaysPreTouch JVM flag Enables the touching of all memory pages used by the JVM heap spaces during initialization of the HotSpot VM, which commits all memory pages at initialization time. By default, pages are committed only as they are needed.
2016-03-03 13:44:56 -05:00
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
include::migrate_5_0/search.asciidoc[]
Script mode settings This commit converts the script mode settings to the new settings infrastructure. This is a major refactoring of the handling of script mode settings. This refactoring is necessary because these settings are determined at runtime based on the registered script engines and the registered script contexts.
2016-01-22 06:50:28 -05:00
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
include::migrate_5_0/mapping.asciidoc[]
Script mode settings This commit converts the script mode settings to the new settings infrastructure. This is a major refactoring of the handling of script mode settings. This refactoring is necessary because these settings are determined at runtime based on the registered script engines and the registered script contexts.
2016-01-22 06:50:28 -05:00
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
include::migrate_5_0/percolator.asciidoc[]
term vectors: The term vector APIs no longer modify the mappings if an unmapped field is found
2016-01-28 04:31:43 -05:00
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
include::migrate_5_0/index-apis.asciidoc[]
Add note on Groovy dependencies to migration docs This commit adds a note to the migration docs regarding the reduction of the Groovy dependencies from the groovy-all artifact to the groovy artifact that was previously done in 180ab2493e96223479c2d5efd9fdd0f28fd12fee. Closes #16858
2016-02-29 09:25:39 -05:00
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
include::migrate_5_0/settings.asciidoc[]
Add note on Groovy dependencies to migration docs This commit adds a note to the migration docs regarding the reduction of the Groovy dependencies from the groovy-all artifact to the groovy artifact that was previously done in 180ab2493e96223479c2d5efd9fdd0f28fd12fee. Closes #16858
2016-02-29 09:25:39 -05:00
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
include::migrate_5_0/allocation.asciidoc[]
term vectors: The term vector APIs no longer modify the mappings if an unmapped field is found
2016-01-28 04:31:43 -05:00
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
include::migrate_5_0/rest.asciidoc[]
add migration notice
2016-02-04 10:23:58 -05:00
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
include::migrate_5_0/cat.asciidoc[]
Make security non-optional 2.x has show so far that running with security manager is the way to go. This commit make this non-optional. Users that need to pass their own rules can still do this via the system configuration for the security manager. They can even opt out of all security that way.
2016-01-22 07:00:50 -05:00
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
include::migrate_5_0/java.asciidoc[]
Make security non-optional 2.x has show so far that running with security manager is the way to go. This commit make this non-optional. Users that need to pass their own rules can still do this via the system configuration for the security manager. They can even opt out of all security that way.
2016-01-22 07:00:50 -05:00
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
include::migrate_5_0/packaging.asciidoc[]
Fail closing or deleting indices during a full snapshot Closes #16321
2016-03-08 15:20:15 -05:00
Reworked 5.0 breaking changes docs
2016-03-13 16:17:48 -04:00
include::migrate_5_0/plugins.asciidoc[]
Fail closing or deleting indices during a full snapshot Closes #16321
2016-03-08 15:20:15 -05:00
Use `mmapfs` by default. I case any problem was discovered, you can still enable the legacy `default` directory instead. But the plan is to get rid of it in 6.0. Closes #16983
2016-04-08 06:18:02 -04:00
include::migrate_5_0/fs.asciidoc[]