2017-08-16 15:12:44 -04:00
|
|
|
[[breaking-changes-7.0]]
|
|
|
|
== Breaking changes in 7.0
|
2018-09-27 11:41:38 -04:00
|
|
|
++++
|
|
|
|
<titleabbrev>7.0</titleabbrev>
|
|
|
|
++++
|
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.
|
|
|
|
|
2018-06-15 14:04:11 -04:00
|
|
|
See also <<release-highlights>> and <<es-release-notes>>.
|
|
|
|
|
2017-08-28 11:43:59 -04:00
|
|
|
* <<breaking_70_aggregations_changes>>
|
2017-08-17 16:57:26 -04:00
|
|
|
* <<breaking_70_cluster_changes>>
|
2018-12-20 08:02:44 -05:00
|
|
|
* <<breaking_70_discovery_changes>>
|
2017-08-17 16:57:26 -04:00
|
|
|
* <<breaking_70_indices_changes>>
|
2017-08-28 11:43:59 -04:00
|
|
|
* <<breaking_70_mappings_changes>>
|
2017-09-07 11:25:05 -04:00
|
|
|
* <<breaking_70_search_changes>>
|
2018-05-02 12:48:49 -04:00
|
|
|
* <<breaking_70_packaging_changes>>
|
2017-09-12 10:51:44 -04:00
|
|
|
* <<breaking_70_plugins_changes>>
|
2017-11-24 07:03:19 -05:00
|
|
|
* <<breaking_70_analysis_changes>>
|
2017-11-17 15:31:52 -05:00
|
|
|
* <<breaking_70_api_changes>>
|
2018-01-25 08:13:20 -05:00
|
|
|
* <<breaking_70_java_changes>>
|
2018-01-03 06:16:42 -05:00
|
|
|
* <<breaking_70_settings_changes>>
|
2018-05-19 00:26:26 -04:00
|
|
|
* <<breaking_70_scripting_changes>>
|
2018-05-25 15:04:50 -04:00
|
|
|
* <<breaking_70_snapshotstats_changes>>
|
2018-06-12 15:00:06 -04:00
|
|
|
* <<breaking_70_restclient_changes>>
|
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>>
|
2017-08-17 16:57:26 -04:00
|
|
|
|
2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
|
|
|
=== Indices created before 7.0
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
=========================================
|
|
|
|
|
2017-08-28 11:43:59 -04:00
|
|
|
include::migrate_7_0/aggregations.asciidoc[]
|
2017-11-24 12:16:14 -05:00
|
|
|
include::migrate_7_0/analysis.asciidoc[]
|
2017-08-17 16:57:26 -04:00
|
|
|
include::migrate_7_0/cluster.asciidoc[]
|
2018-12-20 08:02:44 -05:00
|
|
|
include::migrate_7_0/discovery.asciidoc[]
|
2017-08-17 16:57:26 -04:00
|
|
|
include::migrate_7_0/indices.asciidoc[]
|
2017-08-28 11:43:59 -04:00
|
|
|
include::migrate_7_0/mappings.asciidoc[]
|
2017-09-07 11:25:05 -04:00
|
|
|
include::migrate_7_0/search.asciidoc[]
|
2018-05-02 12:48:49 -04:00
|
|
|
include::migrate_7_0/packaging.asciidoc[]
|
2017-09-12 10:51:44 -04:00
|
|
|
include::migrate_7_0/plugins.asciidoc[]
|
2017-11-17 15:31:52 -05:00
|
|
|
include::migrate_7_0/api.asciidoc[]
|
2018-01-25 08:13:20 -05:00
|
|
|
include::migrate_7_0/java.asciidoc[]
|
2018-01-03 06:16:42 -05:00
|
|
|
include::migrate_7_0/settings.asciidoc[]
|
2018-05-19 00:26:26 -04:00
|
|
|
include::migrate_7_0/scripting.asciidoc[]
|
2018-06-12 15:00:06 -04:00
|
|
|
include::migrate_7_0/snapshotstats.asciidoc[]
|
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[]
|