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_2_0.asciidoc

54 lines
1.5 KiB
Plaintext
Raw Normal View History

Docs: Added breaking changes docs for Indices APIs Adds the breaking changes defaults for the change of default indices options for the GET Aliases API
2014-09-30 05:54:50 -04:00
[[breaking-changes-2.0]]
== Breaking changes in 2.0
This section discusses the changes that you need to be aware of when migrating
your application to Elasticsearch 2.0.
Docs: Updated annotations for 2.0.0-beta1
2015-08-14 04:51:09 -04:00
[float]
=== Indices created before 0.90
Elasticsearch 2.0 can read indices created in version 0.90 and above. If any
of your indices were created before 0.90 you will need to upgrade to the
latest 1.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.
[float]
=== Elasticsearch migration plugin
We have provided the https://github.com/elastic/elasticsearch-migration[Elasticsearch migration plugin]
to help you detect any issues that you may have when upgrading to
Elasticsearch 2.0. Please install and run the plugin *before* upgrading.
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/removals.asciidoc[]
Docs: Mention in migration doc that order to dynamic arguments is important Due to the limited abilities of parsing of dynamic (not configured) arguments like `http.cors.enabled`, that dont map to a command line argument but will become configuration, we need to mention explicitely, that those dynamic arguments must come last. Also fixed some mentions of a memory index setting, that does not exist anymore. Closes #12758
2015-08-10 04:41:11 -04:00
Docs: Added a networking section to migrating changes and mentioned multicast removal
2015-08-25 11:53:44 -04:00
include::migrate_2_0/network.asciidoc[]
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/striping.asciidoc[]
Docs: Mention in migration doc that order to dynamic arguments is important Due to the limited abilities of parsing of dynamic (not configured) arguments like `http.cors.enabled`, that dont map to a command line argument but will become configuration, we need to mention explicitely, that those dynamic arguments must come last. Also fixed some mentions of a memory index setting, that does not exist anymore. Closes #12758
2015-08-10 04:41:11 -04:00
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/mapping.asciidoc[]
Docs: Mention in migration doc that order to dynamic arguments is important Due to the limited abilities of parsing of dynamic (not configured) arguments like `http.cors.enabled`, that dont map to a command line argument but will become configuration, we need to mention explicitely, that those dynamic arguments must come last. Also fixed some mentions of a memory index setting, that does not exist anymore. Closes #12758
2015-08-10 04:41:11 -04:00
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/crud.asciidoc[]
added breaking docs
2015-07-09 06:07:49 -04:00
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/query_dsl.asciidoc[]
Removing TransportSingleCustomOperationAction in favour of TransportSingleShardAction to clean up code. The TransportSingleCustomOperationAction `prefer_local` option has been removed as it isn't worth the effort. The TransportSingleShardAction will execute the operation on the receiving node if a concrete list doesn't provide a list of candite shards routings to perform the operation on.
2015-07-21 10:44:58 -04:00
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/search.asciidoc[]
Removing TransportSingleCustomOperationAction in favour of TransportSingleShardAction to clean up code. The TransportSingleCustomOperationAction `prefer_local` option has been removed as it isn't worth the effort. The TransportSingleShardAction will execute the operation on the receiving node if a concrete list doesn't provide a list of candite shards routings to perform the operation on.
2015-07-21 10:44:58 -04:00
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/aggs.asciidoc[]
Removing TransportSingleCustomOperationAction in favour of TransportSingleShardAction to clean up code. The TransportSingleCustomOperationAction `prefer_local` option has been removed as it isn't worth the effort. The TransportSingleShardAction will execute the operation on the receiving node if a concrete list doesn't provide a list of candite shards routings to perform the operation on.
2015-07-21 10:44:58 -04:00
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/parent_child.asciidoc[]
Remove the `node.enable_custom_paths` setting This setting is useless now that we have the `path.shared_data` setting. Resolves #12776
2015-08-12 13:25:57 -04:00
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/scripting.asciidoc[]
Remove the `node.enable_custom_paths` setting This setting is useless now that we have the `path.shared_data` setting. Resolves #12776
2015-08-12 13:25:57 -04:00
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/index_apis.asciidoc[]
Remove the `node.enable_custom_paths` setting This setting is useless now that we have the `path.shared_data` setting. Resolves #12776
2015-08-12 13:25:57 -04:00
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/snapshot_restore.asciidoc[]
Remove the `node.enable_custom_paths` setting This setting is useless now that we have the `path.shared_data` setting. Resolves #12776
2015-08-12 13:25:57 -04:00
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/packaging.asciidoc[]
Remove the `node.enable_custom_paths` setting This setting is useless now that we have the `path.shared_data` setting. Resolves #12776
2015-08-12 13:25:57 -04:00
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/settings.asciidoc[]
Remove the `node.enable_custom_paths` setting This setting is useless now that we have the `path.shared_data` setting. Resolves #12776
2015-08-12 13:25:57 -04:00
Docs: Rewrote the migrating-to-2.0 section
2015-08-14 14:26:06 -04:00
include::migrate_2_0/stats.asciidoc[]
Remove the `node.enable_custom_paths` setting This setting is useless now that we have the `path.shared_data` setting. Resolves #12776
2015-08-12 13:25:57 -04:00
Mapping: Default position_offset_gap to 100 This is much more fiddly than you'd expect it to be because of the way position_offset_gap is applied in StringFieldMapper. Instead of setting the default to 100 its simpler to make sure that all the analyzers default to 100 and that StringFieldMapper doesn't override the default unless the user specifies something different. Unless the index was created before 2.1, in which case the old default of 0 has to take. Also postition_offset_gaps less than 0 aren't allowed at all. New tests test that: 1. the new default doesn't match phrases across values with reasonably low slop (5) 2. the new default doest match phrases across values with reasonably high slop (50) 3. you can override the value and phrases work as you'd expect 4. if you leave the value undefined in the mapping and define it on a custom analyzer the the value from the custom analyzer shines through Closes #7268
2015-07-29 17:07:26 -04:00
include::migrate_2_0/java.asciidoc[]