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

Elasticsearch version 6.3.2

edit

Elasticsearch version 6.3.2

edit

Also see 6.3.

Bug fixes

edit
Allocation
  • A replica can be promoted and started in one cluster state update #32042
Authentication
  • Fix building AD URL from domain name #31849
Core
  • Disable C2 from using AVX-512 on JDK 10 #32138 (issue: #31425)
Machine Learning
  • Fixes calendar and filter updates from non-master nodes #31804 (issue: #31803)
  • No longer treats stale FAILED jobs as OPENING in job allocation #31800 (issue: #31794)
  • Rate limits established model memory updates #31768
  • Fixes SIGSEGV when upgrading a job directly from 5.6.10 to 6.3. It also fixes the upgrade for the trend component model, which caused large prediction errors immediately after upgrading. #143 (issue: #141)
  • Fixes issues upgrading the state, which could cause the autodetect process to crash. #140 (issue: #136)
Recovery
  • X-pack rolling upgrade failures [ISSUE] #31827
Rollup
  • Histo group config should support scaled_floats #32048 (issue: #32035)
SQL
  • HAVING clause should accept only aggregates #31872 (issue: #31726)
  • Fix incorrect HAVING equality #31820 (issue: #31796)
  • Fix incorrect message for aliases #31792 (issue: #31611)
  • Fix querying an alias having different mappings indices generates an incorrect error message [ISSUE] #31784
  • Allow long literals #31777 (issue: #31750)
  • Fix stackoverflow on getObject and timestamp conversion #31735 (issue: #31734)
Security
  • Detect old trial licenses and mimic behaviour #32209
Watcher
  • Add ssl.trust email account setting #31684
  • Fix check for currently executed watches #31137
  • Increase HttpClient parallel sent requests #31859 (issue: #30130)
« Release Notes Elasticsearch version 6.3.1 »