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

75 lines
1.9 KiB
Plaintext
Raw Normal View History

Add breaking changes for 6.0
2016-09-08 12:27:01 -04:00
[[breaking-changes-6.0]]
== Breaking changes in 6.0
This section discusses the changes that you need to be aware of when migrating
your application to Elasticsearch 6.0.
[float]
=== Indices created before 6.0
Elasticsearch 6.0 can read indices created in version 5.0 or above. An
Elasticsearch 6.0 node will not start in the presence of indices created in a
version of Elasticsearch before 5.0.
[IMPORTANT]
.Reindex indices from Elasticseach 2.x or before
=========================================
Indices created in Elasticsearch 2.x or before will need to be reindexed with
Elasticsearch 5.x in order to be readable by Elasticsearch 6.x. The easiest
way to reindex old indices is to use the `reindex` API.
=========================================
[float]
=== Also see:
Add migration docs for cat API This commit adds migration docs for the cat API, including a note regarding the change in response in the cat thread pool API for unbounded queue sizes. Relates #21342
2016-11-09 07:06:41 -05:00
* <<breaking_60_cat_changes>>
Add information about the removal of store throttling to the migration guide. Relates to #21573
2016-11-21 09:02:34 -05:00
* <<breaking_60_stats_changes>>
Remove allow unquoted JSON Previous versions of Elasticsearch permitted unquoted JSON field names even though this is against the JSON spec. This leniency was disabled by default in the 5.x series of Elasticsearch but a backwards compatibility layer was added via a system property with the intention of removing this layer in 6.0.0. This commit removes this backwards compatibility layer. Relates #20388
2016-09-08 13:36:31 -04:00
* <<breaking_60_rest_changes>>
* <<breaking_60_search_changes>>
Remove support for the include/pattern syntax. (#23141) Relates #22933
2017-03-01 04:00:38 -05:00
* <<breaking_60_aggregations_changes>>
Throw an exception on unrecognized "match_mapping_type" When using dynamic templates, ES will now throw an exception if a `match_mapping_type` is used that doesn't correspond to an actual type. Relates to #17285
2016-12-09 16:36:45 -05:00
* <<breaking_60_mappings_changes>>
No longer allow cluster name in data path In 5.x we allowed this with a deprecation warning. This removes the code added for that deprecation, requiring the cluster name to not be in the data path. Resolves #20391
2016-09-12 17:47:01 -04:00
* <<breaking_60_docs_changes>>
* <<breaking_60_cluster_changes>>
Docs: add documentation about removal of cluster.routing.allocation.snapshot.relocation_enabled
2016-10-18 12:35:57 -04:00
* <<breaking_60_settings_changes>>
Remove mapper attachments plugin We now have in 5.0.0 `ingest-attachment` plugin. We can remove `mapper-attachments` plugin for 6.0. Closes #18837.
2016-09-12 09:54:12 -04:00
* <<breaking_60_plugins_changes>>
Breaking changes docs for template index_patterns 0219a211d3539781ad4bc59bbb68ab9dd5633090 added support for templates to have multiple patterns and renamed `template` to `index_patterns`. This adds the breaking changes docs for that.
2016-11-11 10:11:46 -05:00
* <<breaking_60_indices_changes>>
Remove groovy scripting language (#21607) * Scripting: Remove groovy scripting language Groovy was deprecated in 5.0. This change removes it, along with the legacy default language infrastructure in scripting.
2016-11-22 22:24:12 -05:00
* <<breaking_60_scripting_changes>>
Change type of ingest doc meta-data field 'TIMESTAMP' to `Date` (#22234) With this commit we change the data type of the 'TIMESTAMP' meta-data field from a formatted date string to a plain `java.util.Date` instance. The main reason for this change is that our benchmarks have indicated that this contributes significantly to the time spent in the ingest pipeline. The overhead in terms of indexing throughput of the ingest pipeline is about 15% and breaks down roughly as follows: * 5% overhead caused by the conversion from `XContent` -> `Map` * 5% overhead caused by the timestamp formatting * 5% overhead caused by the conversion `Map` -> `XContent` Relates #22074
2016-12-19 03:10:58 -05:00
* <<breaking_60_ingest_changes>>
percolator: remove deprecated percolate and mpercolate apis
2016-12-22 11:57:47 -05:00
* <<breaking_60_percolator_changes>>
Enforce Content-Type requirement on the rest layer and remove deprecated methods (#23146) This commit enforces the requirement of Content-Type for the REST layer and removes the deprecated methods in transport requests and their usages. While doing this, it turns out that there are many places where *Entity classes are used from the apache http client libraries and many of these usages did not specify the content type. The methods that do not specify a content type explicitly have been added to forbidden apis to prevent more of these from entering our code base. Relates #19388
2017-02-17 14:45:41 -05:00
* <<breaking_60_java_changes>>
Remove customization of ES_USER and ES_GROUP This removes the ability to configure Elasticsearch to use custom username and/or group when it is run. Resolves #23848
2017-04-07 16:21:35 -04:00
* <<breaking_60_packaging_changes>>
Add breaking changes for 6.0
2016-09-08 12:27:01 -04:00
Add migration docs for cat API This commit adds migration docs for the cat API, including a note regarding the change in response in the cat thread pool API for unbounded queue sizes. Relates #21342
2016-11-09 07:06:41 -05:00
include::migrate_6_0/cat.asciidoc[]
Add information about the removal of store throttling to the migration guide. Relates to #21573
2016-11-21 09:02:34 -05:00
include::migrate_6_0/stats.asciidoc[]
Remove allow unquoted JSON Previous versions of Elasticsearch permitted unquoted JSON field names even though this is against the JSON spec. This leniency was disabled by default in the 5.x series of Elasticsearch but a backwards compatibility layer was added via a system property with the intention of removing this layer in 6.0.0. This commit removes this backwards compatibility layer. Relates #20388
2016-09-08 13:36:31 -04:00
include::migrate_6_0/rest.asciidoc[]
include::migrate_6_0/search.asciidoc[]
Remove FORCE version_type This was an error-prone version type that allowed overriding previous version semantics. It could cause primaries and replicas to be out of sync however, so it has been removed. Resolves #19769
2016-09-07 13:00:09 -04:00
Remove support for the include/pattern syntax. (#23141) Relates #22933
2017-03-01 04:00:38 -05:00
include::migrate_6_0/aggregations.asciidoc[]
Throw an exception on unrecognized "match_mapping_type" When using dynamic templates, ES will now throw an exception if a `match_mapping_type` is used that doesn't correspond to an actual type. Relates to #17285
2016-12-09 16:36:45 -05:00
include::migrate_6_0/mappings.asciidoc[]
Remove FORCE version_type This was an error-prone version type that allowed overriding previous version semantics. It could cause primaries and replicas to be out of sync however, so it has been removed. Resolves #19769
2016-09-07 13:00:09 -04:00
include::migrate_6_0/docs.asciidoc[]
No longer allow cluster name in data path In 5.x we allowed this with a deprecation warning. This removes the code added for that deprecation, requiring the cluster name to not be in the data path. Resolves #20391
2016-09-12 17:47:01 -04:00
include::migrate_6_0/cluster.asciidoc[]
Remove mapper attachments plugin We now have in 5.0.0 `ingest-attachment` plugin. We can remove `mapper-attachments` plugin for 6.0. Closes #18837.
2016-09-12 09:54:12 -04:00
Docs: add documentation about removal of cluster.routing.allocation.snapshot.relocation_enabled
2016-10-18 12:35:57 -04:00
include::migrate_6_0/settings.asciidoc[]
Remove mapper attachments plugin We now have in 5.0.0 `ingest-attachment` plugin. We can remove `mapper-attachments` plugin for 6.0. Closes #18837.
2016-09-12 09:54:12 -04:00
include::migrate_6_0/plugins.asciidoc[]
Breaking changes docs for template index_patterns 0219a211d3539781ad4bc59bbb68ab9dd5633090 added support for templates to have multiple patterns and renamed `template` to `index_patterns`. This adds the breaking changes docs for that.
2016-11-11 10:11:46 -05:00
include::migrate_6_0/indices.asciidoc[]
Remove groovy scripting language (#21607) * Scripting: Remove groovy scripting language Groovy was deprecated in 5.0. This change removes it, along with the legacy default language infrastructure in scripting.
2016-11-22 22:24:12 -05:00
include::migrate_6_0/scripting.asciidoc[]
Change type of ingest doc meta-data field 'TIMESTAMP' to `Date` (#22234) With this commit we change the data type of the 'TIMESTAMP' meta-data field from a formatted date string to a plain `java.util.Date` instance. The main reason for this change is that our benchmarks have indicated that this contributes significantly to the time spent in the ingest pipeline. The overhead in terms of indexing throughput of the ingest pipeline is about 15% and breaks down roughly as follows: * 5% overhead caused by the conversion from `XContent` -> `Map` * 5% overhead caused by the timestamp formatting * 5% overhead caused by the conversion `Map` -> `XContent` Relates #22074
2016-12-19 03:10:58 -05:00
include::migrate_6_0/ingest.asciidoc[]
percolator: remove deprecated percolate and mpercolate apis
2016-12-22 11:57:47 -05:00
include::migrate_6_0/percolator.asciidoc[]
Enforce Content-Type requirement on the rest layer and remove deprecated methods (#23146) This commit enforces the requirement of Content-Type for the REST layer and removes the deprecated methods in transport requests and their usages. While doing this, it turns out that there are many places where *Entity classes are used from the apache http client libraries and many of these usages did not specify the content type. The methods that do not specify a content type explicitly have been added to forbidden apis to prevent more of these from entering our code base. Relates #19388
2017-02-17 14:45:41 -05:00
include::migrate_6_0/java.asciidoc[]
Remove customization of ES_USER and ES_GROUP This removes the ability to configure Elasticsearch to use custom username and/or group when it is run. Resolves #23848
2017-04-07 16:21:35 -04:00
include::migrate_6_0/packaging.asciidoc[]