A number of duplicate parameters deprecated in 6.x have been removed from Bulk request, Multi Get request, Term Vectors request, and More Like This Query requests.
The following camel case parameters have been removed:
The following parameters starting with underscore have been removed:
Instead of these removed parameters, use their non camel case equivalents without
starting underscore, e.g. use
version_type instead of
In previous versions of Elasticsearch, the thread pool info returned in the
nodes info API returned
max values reflecting
the configured minimum and maximum number of threads that could be in each
thread pool. The trouble with this representation is that it does not align with
the configuration parameters used to configure thread pools. For
scaling thread pools, the minimum number of threads is
configured by a parameter called
core and the maximum number of threads is
configured by a parameter called
max. For fixed thread pools, there is only one configuration parameter along these lines and that
parameter is called
size, reflecting the fixed number of threads in the
pool. This discrepancy between the API and the configuration parameters has been
rectified. Now, the API will report
max for scaling thread pools,
size for fixed thread pools.
Similarly, in the cat thread pool API the existing
size output has been
pool_size which reflects the number of threads currently in the
pool; the shortcut for this value has been changed from
output has been renamed to
core with a shortcut of
cr, the shortcut for
max has been changed to
mx, and the
size output with a shortcut of
has been reused to report the configured number of threads in the pool. This
aligns the output of the API with the configuration values for thread
pools. Note that
max will be populated for scaling thread pools,
size will be populated for fixed thread pools.
and Update request. The Update API returns
400 - Bad request if request contains
unknown parameters (instead of ignored in the previous version).
suggest stats were folded into
search stats. Support for the
suggest metric on the indices stats and nodes stats APIs remained for
backwards compatibility. Backwards support for the
suggest metric was
deprecated in 6.3.0 and now removed in 7.0.0.
In the past,
fields could be provided either as a parameter, or as part of the request
fields in the request body as opposed to a parameter was deprecated
in 6.4.0, and is now unsupported in 7.0.0.
Versions of Elasticsearch prior to 6.4.0 did not copy index settings on shrink
and split operations. Starting with Elasticsearch 7.0.0, the default behavior
will be for such settings to be copied on such operations. To enable users in
6.4.0 to transition in 6.4.0 to the default behavior in 7.0.0, the
copy_settings parameter was added on the REST layer. As this behavior will be
the only behavior in 8.0.0, this parameter is deprecated in 7.0.0 for removal in
When putting stored scripts, support for storing them with the deprecated
template context or without a context is
now removed. Scripts must be stored using the
script context as mentioned in the documentation.
The behavior and response codes of the get aliases API no longer vary depending on whether X-Pack security is enabled. Previously a 404 - NOT FOUND (IndexNotFoundException) could be returned in case the current user was not authorized for any alias. An empty response with status 200 - OK is now returned instead at all times.
The Put User API response was changed in 6.5.0 to add the
outside of the user object where it previously had been. In 7.0.0 the user
object has been removed in favor of the top level