WARNING: Version 5.4 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Breaking changes in 5.3edit
Packaging changesedit
Logging configurationedit
Previously Elasticsearch exposed a single system property (es.logs
) that
included the absolute path to the configured logs directory, and the prefix of
the filenames used for the various logging files (the main log file, the
deprecation log, and the slow logs). This property has been replaced in favor of
three properties:
-
es.logs.base_path
: the absolute path to the configured logs directory -
es.logs.cluster_name
: the default prefix of the filenames used for the various logging files -
es.logs.node_name
: exposed ifnode.name
is configured for inclusion in the filenames of the various logging files (if you prefer)
The property es.logs
is deprecated and will be removed in Elasticsearch 6.0.0.
Use of Netty 3 is deprecatededit
Usage of Netty 3 for transport (transport.type=netty3
) or HTTP
(http.type=netty3
) is deprecated and will be removed in Elasticsearch
6.0.0.
Settings changesedit
Lenient boolean representations are deprecatededit
Usage of any value other than false
, "false"
, true
and "true"
in boolean
settings deprecated.
REST API changesedit
Lenient boolean representations are deprecatededit
Usage of any value other than false
, "false"
, true
and "true"
for
boolean request parameters and boolean properties in the body of REST API calls
is deprecated.
Mapping changesedit
Lenient boolean representations are deprecatededit
Usage of any value other than false
, "false"
, true
and "true"
for
boolean values in mappings is deprecated.