WARNING: Version 1.6 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.
This section discusses the changes that you need to be aware of when migrating your application from Elasticsearch 1.x to Elasticsearch 1.6.
The More Like This API query has been deprecated and will be removed in 2.0. Instead use the More Like This Query.
top_children query has been deprecated and will be removed in 2.0. Instead the
has_child query should be used.
top_children query isn’t always faster than the
has_child query and the
top_children query is often inaccurate.
The total hits and any aggregations in the same search request will likely be off.
Locations of file system repositories has to be now registered using
path.repo setting. The
setting can contain one or more repository locations:
path.repo: ["/mnt/daily", "/mnt/weekly"]
If the file system repository location is specified as an absolute path it has to start with one of the locations
path.repo. If the location is specified as a relative path, it will be resolved against the first
location specified in the
Starting with version 1.6.1 URL repositories with
ftp: URLs has to be whitelisted by specifying allowed URLs in the
repositories.url.allowed_urls setting. This setting supports wildcards in the place of host, path, query, and
fragment. For example:
repositories.url.allowed_urls: ["http://www.example.org/root/*", "https://*.mydomain.com/*?*#*"]