IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Elasticsearch version 6.1.3 Elasticsearch version 6.1.1 »
Elastic Docs ›Elasticsearch Guide [6.3] ›Release Notes

Elasticsearch version 6.1.2

edit

Elasticsearch version 6.1.2

edit

Enhancements

edit
Internal
  • Make AbstractQueryBuilder.declareStandardFields to be protected (#27865) #27894 (issue: #27865)

Bug Fixes

edit
Aggregations
  • Fix incorrect results for aggregations nested under a nested aggregation #27946 (issue: #27912)
  • Fix composite aggregation when after term is missing in the shard #27936
  • Fix preserving FiltersAggregationBuilder#keyed field on rewrite #27900 (issue: #27841)
Engine
  • Use _refresh to shrink the version map on inactivity #27918 (issue: #27852)
  • Allow resize version map under lock even if there are pending operations #27870 (issue: #27852)
Machine Learning
  • Fixed the removal of tokens during categorization, where the tokens were incorrectly deemed to be hexadecimal numbers. For more information, see Categorizing log messages.
  • Reduced the sensitivity of the analysis to small perturbations in the input data.
  • Disabled the ability to create forecasts for jobs that were created before 6.1.0.
Monitoring
  • Added a cluster_alerts.management.blacklist setting for HTTP Exporters, which you can use to block the creation of specific cluster alerts. For more information, see Monitoring Settings.
Network
  • Only bind loopback addresses when binding to local #28029
Recovery
  • Allow shrinking of indices from a previous major #28076 (issue: #28061)
Search
  • Use the underlying connection version for CCS connections #28093
  • Carry forward weights, etc on rescore rewrite #27981 (issue: #27979)
Security
  • Fixed an issue in the Active Directory realm when following referrals that resulted in an increase in the number of connections made to Active Directory.
  • Fixed exception that occurred when using auditing and transport clients. In particular, the problem occurred when the number of processors on the transport client did not match the number of processors on the server.
  • Ensured that TLS is not required to install a license if you are using single-node discovery. For more information, see Single-node discovery and Setting up TLS on a Cluster.
  • Fixed the has_privileges API. In particular, the has_all_requested field in the API results was not taking cluster privileges into consideration.
Snapshot/Restore
  • Fail restore when the shard allocations max retries count is reached #27493 (issue: #26865)
Translog
Watcher
  • Fixed encoding of UTF-8 data in the HTTP client.
« Elasticsearch version 6.1.3 Elasticsearch version 6.1.1 »