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

78 lines
2.5 KiB
Plaintext
Raw Normal View History

Migrate migration docs from 6.0 to 7.0 (#26227) * Migrate migration docs from 6.0 to 7.0 Since we only keep one version of migration docs and master is now on 7.0, we should migrate these so breaking changes can be added in the right place. * Remove release notes as well They link to the migration guides, so they have to go. * Add placeholder notes for 7.0 so doc build is happy
2017-08-16 15:12:44 -04:00
[[breaking-changes-7.0]]
== Breaking changes in 7.0
[DOCS] Synchronize location of Breaking Changes (#33588)
2018-09-27 11:41:38 -04:00
++++
<titleabbrev>7.0</titleabbrev>
++++
Migrate migration docs from 6.0 to 7.0 (#26227) * Migrate migration docs from 6.0 to 7.0 Since we only keep one version of migration docs and master is now on 7.0, we should migrate these so breaking changes can be added in the right place. * Remove release notes as well They link to the migration guides, so they have to go. * Add placeholder notes for 7.0 so doc build is happy
2017-08-16 15:12:44 -04:00
This section discusses the changes that you need to be aware of when migrating
your application to Elasticsearch 7.0.
[DOCS] Adds links to release notes and highlights
2018-06-15 14:04:11 -04:00
See also <<release-highlights>> and <<es-release-notes>>.
[DOCS] Adds tagged region for notable breaking changes
2019-03-08 14:13:02 -05:00
* <<breaking_70_notable>>
Remove the _all metadata field (#26356) * Remove the _all metadata field This change removes the `_all` metadata field. This field is deprecated in 6 and cannot be activated for indices created in 6 so it can be safely removed in the next major version (e.g. 7).
2017-08-28 11:43:59 -04:00
* <<breaking_70_aggregations_changes>>
Disallow : in cluster and index/alias names (#26247) We use `:` for cross-cluster search (eg `cluster:index`), therefore, we should not allow the ambiguity when allowing cluster or index names. Relates to #23892
2017-08-17 16:57:26 -04:00
* <<breaking_70_cluster_changes>>
[Zen2] Update documentation for Zen2 (#34714) This commit overhauls the documentation of discovery and cluster coordination, removing mention of the Zen Discovery module and replacing it with docs for the new cluster coordination mechanism introduced in 7.0. Relates #32006
2018-12-20 08:02:44 -05:00
* <<breaking_70_discovery_changes>>
Disallow : in cluster and index/alias names (#26247) We use `:` for cross-cluster search (eg `cluster:index`), therefore, we should not allow the ambiguity when allowing cluster or index names. Relates to #23892
2017-08-17 16:57:26 -04:00
* <<breaking_70_indices_changes>>
Remove the _all metadata field (#26356) * Remove the _all metadata field This change removes the `_all` metadata field. This field is deprecated in 6 and cannot be activated for indices created in 6 so it can be safely removed in the next major version (e.g. 7).
2017-08-28 11:43:59 -04:00
* <<breaking_70_mappings_changes>>
Enable adaptive replica selection by default (#26522) Relates to #24915
2017-09-07 11:25:05 -04:00
* <<breaking_70_search_changes>>
Generate release notes for 7.0.0-alpha1. (#39899) We were missing release notes for 7.0.0-alpha1. I generated them by running the release-notes script with a quick hack that filtered out pull requests that had been closed on or after 2018-11-15. Some breaking changes had been documented in the release notes rather than the migration guide so I moved them.
2019-03-12 03:10:18 -04:00
* <<breaking_70_suggesters_changes>>
Packaging: Unmark systemd service file as a config file (#29004) Systemd overrides should happen through /etc/systemd/system, not directly editing the service file. This commit removes marking the service file as configuration for rpm and deb packages.
2018-05-02 12:48:49 -04:00
* <<breaking_70_packaging_changes>>
Remove azure deprecated settings (#26099) Follow up for #23405. We remove azure deprecated settings in 7.0: * The legacy azure settings which where starting with `cloud.azure.storage.` prefix have been removed. This includes `account`, `key`, `default` and `timeout`. You need to use settings which are starting with `azure.client.` prefix instead. * Global timeout setting `cloud.azure.storage.timeout` has been removed. You must set it per azure client instead. Like `azure.client.default.timeout: 10s` for example.
2017-09-12 10:51:44 -04:00
* <<breaking_70_plugins_changes>>
Replace `delimited_payload_filter` by `delimited_payload` (#26625) The `delimited_payload_filter` is renamed to `delimited_payload`, the old name is deprecated and should be replaced by `delimited_payload`. Closes #21978
2017-11-24 07:03:19 -05:00
* <<breaking_70_analysis_changes>>
Standardize underscore requirements in parameters (#27414) Stardardize underscore requirements in parameters across different type of requests: _index, _type, _source, _id keep their underscores params like version and retry_on_conflict will be without underscores Throw an error if older versions of parameters are used BulkRequest, MultiGetRequest, TermVectorcRequest, MoreLikeThisQuery were changed Closes #26886
2017-11-17 15:31:52 -05:00
* <<breaking_70_api_changes>>
Java Api clean up: remove deprecated `isShardsAcked` (#28311) This PR removes previously deprecated `isShardsAcked()` method in favour of `isShardsAcknowledged()` on `CreateIndexResponse`, `CreateIndexClusterStateUpdateResponse` and `RolloverResponse` Related to #27784 Follow-up of #27819
2018-01-25 08:13:20 -05:00
* <<breaking_70_java_changes>>
percolator: remove deprecated map_unmapped_fields_as_string setting
2018-01-03 06:16:42 -05:00
* <<breaking_70_settings_changes>>
Scripting: Remove getDate methods from ScriptDocValues (#30690) The getDate() and getDates() existed prior to 5.x on long fields in scripting. In 5.x, a new Date type for ScriptDocValues was added. The getDate() and getDates() methods were left on long fields and added to date fields to ease the transition. This commit removes those methods for 7.0.
2018-05-19 00:26:26 -04:00
* <<breaking_70_scripting_changes>>
Include size of snapshot in snapshot metadata (#29602) Include size of snapshot in snapshot metadata Adds difference of number of files (and file sizes) between prev and current snapshot. Total number/size reflects total number/size of files in snapshot. Closes #18543
2018-05-25 15:04:50 -04:00
* <<breaking_70_snapshotstats_changes>>
REST high-level Client: remove deprecated API methods (#31200) This commit removes all the API methods that accept a `Header` varargs argument, in favour of the newly introduced API methods that accept a `RequestOptions` argument. Relates to #31069
2018-06-12 15:00:06 -04:00
* <<breaking_70_restclient_changes>>
LLREST: Drop deprecated methods (#33223) In #29623 we added `Request` object flavored requests to the low level REST client and in #30315 we deprecated the old `performRequest`s. In a long series of PRs I've changed all of the old style requests. This drops the deprecated methods and will be released with 7.0.
2018-09-01 11:11:25 -04:00
* <<breaking_70_low_level_restclient_changes>>
Elasticsearch support to JSON logging (#36833) In order to support JSON log format, a custom pattern layout was used and its configuration is enclosed in ESJsonLayout. Users are free to use their own patterns, but if smooth Beats integration is needed, they should use ESJsonLayout. EvilLoggerTests are left intact to make sure user's custom log patterns work fine. To populate additional fields node.id and cluster.uuid which are not available at start time, a cluster state update will have to be received and the values passed to log4j pattern converter. A ClusterStateObserver.Listener is used to receive only one ClusteStateUpdate. Once update is received the nodeId and clusterUUid are set in a static field in a NodeAndClusterIdConverter. Following fields are expected in JSON log lines: type, tiemstamp, level, component, cluster.name, node.name, node.id, cluster.uuid, message, stacktrace see ESJsonLayout.java for more details and field descriptions Docker log4j2 configuration is now almost the same as the one use for ES binary. The only difference is that docker is using console appenders, whereas ES is using file appenders. relates: #32850
2019-01-29 01:20:09 -05:00
* <<breaking_70_logging_changes>>
Fail start on obsolete indices documentation (#37786) Added breaking changes documentation for node start up obsolete indices detection. Issue #27073
2019-01-31 09:40:06 -05:00
* <<breaking_70_node_changes>>
Add documentation about breaking java time changes (#38886) In addition remove joda time mentions across the docs, make sure links are updated to java time javadocs. Forward port of #38720
2019-02-14 04:18:12 -05:00
* <<breaking_70_java_time_changes>>
Disallow : in cluster and index/alias names (#26247) We use `:` for cross-cluster search (eg `cluster:index`), therefore, we should not allow the ambiguity when allowing cluster or index names. Relates to #23892
2017-08-17 16:57:26 -04:00
[DOCS] Synchronize location of Breaking Changes (#33588)
2018-09-27 11:41:38 -04:00
[float]
[DOCS] Adds tagged region for notable breaking changes
2019-03-08 14:13:02 -05:00
[[breaking_70_notable]]
=== Notable changes
// NOTE: The content in this section is also used in the Installation and Upgrade Guide.
//tag::notable-breaking-changes[]
[float]
==== Indices created before 7.0
[DOCS] Synchronize location of Breaking Changes (#33588)
2018-09-27 11:41:38 -04:00
Elasticsearch 7.0 can read indices created in version 6.0 or above. An
Elasticsearch 7.0 node will not start in the presence of indices created in a
version of Elasticsearch before 6.0.
[IMPORTANT]
.Reindex indices from Elasticsearch 5.x or before
=========================================
Indices created in Elasticsearch 5.x or before will need to be reindexed with
Elasticsearch 6.x in order to be readable by Elasticsearch 7.x.
=========================================
[DOCS] Adds tagged region for notable breaking changes
2019-03-08 14:13:02 -05:00
// end::notable-breaking-changes[]
Remove the _all metadata field (#26356) * Remove the _all metadata field This change removes the `_all` metadata field. This field is deprecated in 6 and cannot be activated for indices created in 6 so it can be safely removed in the next major version (e.g. 7).
2017-08-28 11:43:59 -04:00
include::migrate_7_0/aggregations.asciidoc[]
[DOCS] Fixed broken link in breaking changes
2017-11-24 12:16:14 -05:00
include::migrate_7_0/analysis.asciidoc[]
Disallow : in cluster and index/alias names (#26247) We use `:` for cross-cluster search (eg `cluster:index`), therefore, we should not allow the ambiguity when allowing cluster or index names. Relates to #23892
2017-08-17 16:57:26 -04:00
include::migrate_7_0/cluster.asciidoc[]
[Zen2] Update documentation for Zen2 (#34714) This commit overhauls the documentation of discovery and cluster coordination, removing mention of the Zen Discovery module and replacing it with docs for the new cluster coordination mechanism introduced in 7.0. Relates #32006
2018-12-20 08:02:44 -05:00
include::migrate_7_0/discovery.asciidoc[]
Disallow : in cluster and index/alias names (#26247) We use `:` for cross-cluster search (eg `cluster:index`), therefore, we should not allow the ambiguity when allowing cluster or index names. Relates to #23892
2017-08-17 16:57:26 -04:00
include::migrate_7_0/indices.asciidoc[]
Remove the _all metadata field (#26356) * Remove the _all metadata field This change removes the `_all` metadata field. This field is deprecated in 6 and cannot be activated for indices created in 6 so it can be safely removed in the next major version (e.g. 7).
2017-08-28 11:43:59 -04:00
include::migrate_7_0/mappings.asciidoc[]
Enable adaptive replica selection by default (#26522) Relates to #24915
2017-09-07 11:25:05 -04:00
include::migrate_7_0/search.asciidoc[]
Generate release notes for 7.0.0-alpha1. (#39899) We were missing release notes for 7.0.0-alpha1. I generated them by running the release-notes script with a quick hack that filtered out pull requests that had been closed on or after 2018-11-15. Some breaking changes had been documented in the release notes rather than the migration guide so I moved them.
2019-03-12 03:10:18 -04:00
include::migrate_7_0/suggesters.asciidoc[]
Packaging: Unmark systemd service file as a config file (#29004) Systemd overrides should happen through /etc/systemd/system, not directly editing the service file. This commit removes marking the service file as configuration for rpm and deb packages.
2018-05-02 12:48:49 -04:00
include::migrate_7_0/packaging.asciidoc[]
Remove azure deprecated settings (#26099) Follow up for #23405. We remove azure deprecated settings in 7.0: * The legacy azure settings which where starting with `cloud.azure.storage.` prefix have been removed. This includes `account`, `key`, `default` and `timeout`. You need to use settings which are starting with `azure.client.` prefix instead. * Global timeout setting `cloud.azure.storage.timeout` has been removed. You must set it per azure client instead. Like `azure.client.default.timeout: 10s` for example.
2017-09-12 10:51:44 -04:00
include::migrate_7_0/plugins.asciidoc[]
Standardize underscore requirements in parameters (#27414) Stardardize underscore requirements in parameters across different type of requests: _index, _type, _source, _id keep their underscores params like version and retry_on_conflict will be without underscores Throw an error if older versions of parameters are used BulkRequest, MultiGetRequest, TermVectorcRequest, MoreLikeThisQuery were changed Closes #26886
2017-11-17 15:31:52 -05:00
include::migrate_7_0/api.asciidoc[]
Java Api clean up: remove deprecated `isShardsAcked` (#28311) This PR removes previously deprecated `isShardsAcked()` method in favour of `isShardsAcknowledged()` on `CreateIndexResponse`, `CreateIndexClusterStateUpdateResponse` and `RolloverResponse` Related to #27784 Follow-up of #27819
2018-01-25 08:13:20 -05:00
include::migrate_7_0/java.asciidoc[]
percolator: remove deprecated map_unmapped_fields_as_string setting
2018-01-03 06:16:42 -05:00
include::migrate_7_0/settings.asciidoc[]
Scripting: Remove getDate methods from ScriptDocValues (#30690) The getDate() and getDates() existed prior to 5.x on long fields in scripting. In 5.x, a new Date type for ScriptDocValues was added. The getDate() and getDates() methods were left on long fields and added to date fields to ease the transition. This commit removes those methods for 7.0.
2018-05-19 00:26:26 -04:00
include::migrate_7_0/scripting.asciidoc[]
REST high-level Client: remove deprecated API methods (#31200) This commit removes all the API methods that accept a `Header` varargs argument, in favour of the newly introduced API methods that accept a `RequestOptions` argument. Relates to #31069
2018-06-12 15:00:06 -04:00
include::migrate_7_0/snapshotstats.asciidoc[]
LLREST: Drop deprecated methods (#33223) In #29623 we added `Request` object flavored requests to the low level REST client and in #30315 we deprecated the old `performRequest`s. In a long series of PRs I've changed all of the old style requests. This drops the deprecated methods and will be released with 7.0.
2018-09-01 11:11:25 -04:00
include::migrate_7_0/restclient.asciidoc[]
include::migrate_7_0/low_level_restclient.asciidoc[]
Elasticsearch support to JSON logging (#36833) In order to support JSON log format, a custom pattern layout was used and its configuration is enclosed in ESJsonLayout. Users are free to use their own patterns, but if smooth Beats integration is needed, they should use ESJsonLayout. EvilLoggerTests are left intact to make sure user's custom log patterns work fine. To populate additional fields node.id and cluster.uuid which are not available at start time, a cluster state update will have to be received and the values passed to log4j pattern converter. A ClusterStateObserver.Listener is used to receive only one ClusteStateUpdate. Once update is received the nodeId and clusterUUid are set in a static field in a NodeAndClusterIdConverter. Following fields are expected in JSON log lines: type, tiemstamp, level, component, cluster.name, node.name, node.id, cluster.uuid, message, stacktrace see ESJsonLayout.java for more details and field descriptions Docker log4j2 configuration is now almost the same as the one use for ES binary. The only difference is that docker is using console appenders, whereas ES is using file appenders. relates: #32850
2019-01-29 01:20:09 -05:00
include::migrate_7_0/logging.asciidoc[]
Fail start on obsolete indices documentation (#37786) Added breaking changes documentation for node start up obsolete indices detection. Issue #27073
2019-01-31 09:40:06 -05:00
include::migrate_7_0/node.asciidoc[]
Add documentation about breaking java time changes (#38886) In addition remove joda time mentions across the docs, make sure links are updated to java time javadocs. Forward port of #38720
2019-02-14 04:18:12 -05:00
include::migrate_7_0/java_time.asciidoc[]