This section discusses the changes that you need to be aware of when migrating your application to Elasticsearch 7.7.
org.elasticsearch.action now log at
INFO level by defaultedit
The default log level for most loggers is
INFO, but in earlier versions
loggers in the
org.elasticsearch.action.* hierarchy emitted log messages at
DEBUG level by default. This sometimes resulted in a good deal of unnecessary
log noise. From 7.7 onwards the default log level for logger in this hierarchy
INFO, in line with most other loggers. If needed, you can recover the
pre-7.7 default behaviour by adjusting your logging.
Validation for dynamic templatesedit
So far misconfiguration of dynamic templates have been discovered when indexing a document with an unmapped field only. In Elasticsearch 8.0 and later versions, dynamic mappings have stricter validation, done at mapping update time. Invalid updates, such as using incorrect analyzer settings or unknown field types, fail. For indices created in Elasticsearch 7.7 and later version, the update succeeds but emits a warning.
thread_pool.listener.queue_size have been deprecatededit
The listener thread pool is no longer used internally by Elasticsearch. Therefore, these settings have been deprecated. You can safely remove these settings from the configuration of your nodes.
cluster.remote.connect is deprecated in favor of
Previously the setting
cluster.remote.connect was used to configure whether or
not the local node is capable of acting as a remote cluster client in
cross-cluster search and cross-cluster replication. This setting is deprecated
in favor of
node.remote_cluster_client serves the same purpose and identifies
the local node as having the
order will be a required config in version 8.0.0.edit
order config will be required in version 8.0.0 for authentication realm
configuration of any type. If the
order config is missing for a realm, the node
will fail to start.
order uniqueness will be enforced in version 8.0.0.edit
order config of authentication realms must be unique in version 8.0.0.
If you configure more than one realm of any type with the same order, the node will fail to start.
Deprecation of insecure monitoring password settingedit
auth.password setting for the monitoring HTTP exporter has been deprecated and will be
removed in version 8.0.0. Please use the
auth.secure_password setting instead.
Consistent rounding of range queries on
range queries on
date_range field currently can have slightly differently
boundaries than their equivalent query on a pure
date field. This can e.g.
happen when using date math or dates that don’t specify up to the last
millisecond. While queries on
date field round up to the latest millisecond
lte boundaries, the same queries on
date_range fields didn’t
do this. The behavior is now the same for both field types like documented in
Date math and rounding.
Pipeline aggregation validation errorsedit
The pipeline aggregation validation has been moved to the coordinating node. Those errors that used to return HTTP 500s/Internal Server Errors now return 400/Bad Request and we now return a list of validation errors rather than the first one we encounter.
Ignored keyword values are no longer highlightededit
If a keyword value was ignored during indexing because of its length
ignore_above parameter was applied), Elasticsearch doesn’t attempt to
highlight it anymore, which means no highlights are produced for