2018-05-01 13:34:26 -04:00
[[es-release-notes]]
= {es} Release Notes
[partintro]
--
2018-05-03 22:38:19 -04:00
// To add a release, copy and paste the template text
2018-05-03 19:31:32 -04:00
// and add a link to the new section. Note that release subheads must
// be floated and sections cannot be empty.
2018-04-18 10:42:05 -04:00
// Use these for links to issue and pulls. Note issues and pulls redirect one to
// each other on Github, so don't worry too much on using the right prefix.
2018-04-30 17:09:32 -04:00
:issue: https://github.com/elastic/elasticsearch/issues/
:pull: https://github.com/elastic/elasticsearch/pull/
2018-04-18 10:42:05 -04:00
2018-05-01 13:34:26 -04:00
This section summarizes the changes in each release.
* <<release-notes-7.0.0>>
* <<release-notes-6.4.0>>
2018-05-03 19:31:32 -04:00
* <<release-notes-6.3.1>>
2018-05-01 13:34:26 -04:00
--
2018-04-18 10:42:05 -04:00
2018-05-03 22:38:19 -04:00
////
// To add a release, copy and paste the following text, uncomment the relevant
// sections, and add a link to the new section in the list of releases at the
// top of the page. Note that release subheads must be floated and sections
// cannot be empty.
// TEMPLATE:
// [[release-notes-n.n.n]]
// == {es} n.n.n
//[float]
[[breaking-n.n.n]]
//=== Breaking Changes
//[float]
//=== Breaking Java Changes
//[float]
//=== Deprecations
//[float]
//=== New Features
//[float]
//=== Enhancements
//[float]
//=== Bug Fixes
//[float]
//=== Regressions
//[float]
//=== Known Issues
////
2018-05-01 13:34:26 -04:00
[[release-notes-7.0.0]]
== {es} 7.0.0
2018-04-18 10:42:05 -04:00
2018-05-03 22:38:19 -04:00
coming[7.0.0]
2018-05-01 13:34:26 -04:00
[float]
[[breaking-7.0.0]]
2018-04-18 10:42:05 -04:00
=== Breaking Changes
2018-04-19 16:59:58 -04:00
<<write-thread-pool-fallback, Removed `thread_pool.bulk.*` settings and
`es.thread_pool.write.use_bulk_as_display_name` system property>> ({pull}29609[#29609])
2018-05-02 12:48:49 -04:00
<<systemd-service-file-config, Systemd service file is no longer marked as configuration>> ({pull}29004[#29004])
2018-04-24 19:03:48 -04:00
<<remove-suggest-metric, Removed `suggest` metric on stats APIs>> ({pull}29635[#29635])
2018-04-27 19:14:11 -04:00
<<remove-field-caps-body, In field capabilities APIs, removed support for providing fields in the request body>> ({pull}30185[#30185])
2018-05-01 19:05:23 -04:00
Machine Learning::
* The `max_running_jobs` node property is removed in this release. Use the
`xpack.ml.max_open_jobs` setting instead. For more information, see <<ml-settings>>.
2018-05-02 14:42:05 -04:00
* <<remove-http-enabled, Removed `http.enabled` setting>> ({pull}29601[#29601])
2018-05-03 22:38:19 -04:00
//[float]
//=== Breaking Java Changes
2018-05-03 19:31:32 -04:00
[float]
2018-05-02 14:42:05 -04:00
=== Deprecations
2018-05-01 19:05:23 -04:00
Monitoring::
* The `xpack.monitoring.collection.interval` setting can no longer be set to `-1`
to disable monitoring data collection. Use `xpack.monitoring.collection.enabled`
and set it to `false` (its default), which was added in 6.3.0.
Security::
* The fields returned as part of the mappings section by get index, get
mappings, get field mappings, and field capabilities API are now only the
ones that the user is authorized to access in case field level security is enabled.
2018-05-01 13:34:26 -04:00
//[float]
//=== New Features
2018-04-18 10:42:05 -04:00
2018-05-01 13:34:26 -04:00
//[float]
//=== Enhancements
2018-04-18 10:42:05 -04:00
2018-05-01 13:34:26 -04:00
[float]
2018-04-18 10:42:05 -04:00
=== Bug Fixes
2018-05-02 12:00:35 -04:00
Fixed prerelease version of elasticsearch in the `deb` package to sort before GA versions
({pull}29000[#29000])
2018-05-04 18:13:50 -04:00
Respect accept header on requests with no handler ({pull}30383[#30383])
2018-05-04 13:45:16 -04:00
Rollup::
* Validate timezone in range queries to ensure they match the selected job when
searching ({pull}30338[#30338])
2018-05-03 19:31:32 -04:00
[float]
2018-05-02 12:00:35 -04:00
=== Regressions
2018-04-27 10:29:59 -04:00
Fail snapshot operations early when creating or deleting a snapshot on a repository that has been
written to by an older Elasticsearch after writing to it with a newer Elasticsearch version. ({pull}30140[#30140])
2018-05-02 15:22:55 -04:00
Fix NPE when CumulativeSum agg encounters null value/empty bucket ({pull}29641[#29641])
2018-05-03 22:38:19 -04:00
//[float]
//=== Regressions
2018-05-01 13:34:26 -04:00
//[float]
//=== Known Issues
2018-04-18 10:42:05 -04:00
2018-05-01 13:34:26 -04:00
[[release-notes-6.4.0]]
== {es} 6.4.0
2018-04-18 10:42:05 -04:00
2018-05-03 22:38:19 -04:00
coming[6.4.0]
//[float]
[[breaking-6.4.0]]
//=== Breaking Changes
//[float]
//=== Breaking Java Changes
//[float]
//=== Deprecations
2018-05-02 04:47:02 -04:00
[float]
=== New Features
The new <<mapping-ignored-field,`_ignored`>> field allows to know which fields
got ignored at index time because of the <<ignore-malformed,`ignore_malformed`>>
option. ({pull}30140[#29658])
2018-04-18 10:42:05 -04:00
2018-05-04 14:46:13 -04:00
A new analysis plugin called `analysis_nori` that exposes the Lucene Korean
analysis module. ({pull}30397[#30397])
2018-05-01 13:34:26 -04:00
[float]
2018-04-18 10:42:05 -04:00
=== Enhancements
2018-05-01 16:20:19 -04:00
{ref-64}/breaking_64_api_changes.html#copy-source-settings-on-resize[Allow copying source settings on index resize operations] ({pull}30255[#30255])
2018-05-01 08:46:12 -04:00
2018-05-01 14:31:23 -04:00
Added new "Request" object flavored request methods. Prefer these instead of the
multi-argument versions. ({pull}29623[#29623])
Watcher: Make start/stop cycle more predictable and synchronous (#30118)
The current implementation starts/stops watcher using an executor. This
can result in our of order operations.
This commit reduces those executor calls to an absolute minimum in order
to be able to do state changes within the cluster state listener method,
which runs in sequence.
When a state change occurs that forces the watcher service to pause
(like no watcher index, no master node, no local shards), the service is
now in a paused state.
Pausing is a super lightweight operation, which marks the
ExecutionService as paused and waits for the currently executing watches
to finish in the background via an executor. The same applies for
stopping, the potentially long running operation is outsourced in to an
executor, as waiting for executed watches is decoupled from the current
state.
The only other long running operation is starting, where watches need to
be loaded. This is also done via an executor, but has an additional
protection by checking the cluster state version it was started with. If
another cluster state version was trying to load the watches, then this
loading will not take effect.
This PR also cleans up some unused states, like the a simple boolean in
the HistoryStore/TriggeredWatchStore marking it as started or stopped,
as this can now be caught in the execution service.
Another advantage of this approach is the fact, that now only triggered
watches are not getting executed, while watches that are run via the
Execute Watch API will still be executed regardless if watcher is
stopped or not.
Lastly the TickerScheduleTriggerEngine thread now only starts on data nodes.
2018-05-03 03:47:12 -04:00
The cluster state listener to decide if watcher should be
stopped/started/paused now runs far less code in an executor but is more
synchronous and predictable. Also the trigger engine thread is only started on
data nodes. And the Execute Watch API can be triggered regardless is watcher is
started or stopped. ({pull}30118[#30118])
2018-05-01 14:31:23 -04:00
2018-05-01 13:34:26 -04:00
[float]
2018-04-18 10:42:05 -04:00
=== Bug Fixes
2018-04-30 07:31:36 -04:00
Do not ignore request analysis/similarity settings on index resize operations when the source index already contains such settings ({pull}30216[#30216])
2018-05-02 15:22:55 -04:00
Fix NPE when CumulativeSum agg encounters null value/empty bucket ({pull}29641[#29641])
2018-05-01 14:31:23 -04:00
2018-05-03 10:08:24 -04:00
Machine Learning::
* Account for gaps in data counts after job is reopened ({pull}30294[#30294])
2018-05-04 13:45:16 -04:00
Rollup::
* Validate timezone in range queries to ensure they match the selected job when
searching ({pull}30338[#30338])
2018-05-03 19:31:32 -04:00
//[float]
//=== Regressions
//[float]
//=== Known Issues
2018-05-03 22:38:19 -04:00
[[release-notes-6.3.1]]
== Elasticsearch version 6.3.1
2018-05-03 19:31:32 -04:00
2018-05-03 22:38:19 -04:00
coming[6.3.1]
2018-05-03 19:31:32 -04:00
//[float]
2018-05-03 22:38:19 -04:00
[[breaking-6.3.1]]
2018-05-03 19:31:32 -04:00
//=== Breaking Changes
//[float]
//=== Breaking Java Changes
//[float]
//=== Deprecations
//[float]
//=== New Features
//[float]
//=== Enhancements
2018-05-03 22:38:19 -04:00
[float]
=== Bug Fixes
Reduce the number of object allocations made by {security} when resolving the indices and aliases for a request ({pull}30180[#30180])
2018-05-03 14:48:23 -04:00
2018-05-01 13:34:26 -04:00
//[float]
//=== Regressions
2018-04-18 10:42:05 -04:00
2018-05-01 13:34:26 -04:00
//[float]
//=== Known Issues