honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/docs/CHANGELOG.asciidoc

258 lines
7.0 KiB
Plaintext
Raw Normal View History

[DOCS] Adds changelog to Elasticsearch Reference (#30271)
2018-05-01 13:34:26 -04:00
[[es-release-notes]]
= {es} Release Notes
[partintro]
--
Client: Deprecate many argument performRequest (#30315) Deprecate the many arguments versions of `performRequest` and `performRequestAsync` in favor of the `Request` object flavored variants introduced in #29623. We'll be dropping the many arguments variants in 7.0 because they make it difficult to add new features in a backwards compatible way and they create a *ton* of intellisense noise.
2018-05-08 14:38:55 -04:00
// To add a release, copy and paste the template text
[DOCS] Commented out empty sections in the changelog to fix the doc build. (#30372)
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.
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
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.
Fix macros in changelog (#30269) remove comments for macros which caused macros not to work correctly
2018-04-30 17:09:32 -04:00
:issue: https://github.com/elastic/elasticsearch/issues/
:pull: https://github.com/elastic/elasticsearch/pull/
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
2018-04-18 10:42:05 -04:00
[DOCS] Adds changelog to Elasticsearch Reference (#30271)
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>>
[DOCS] Commented out empty sections in the changelog to fix the doc build. (#30372)
2018-05-03 19:31:32 -04:00
* <<release-notes-6.3.1>>
[DOCS] Adds changelog to Elasticsearch Reference (#30271)
2018-05-01 13:34:26 -04:00
--
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
2018-04-18 10:42:05 -04:00
[DOCS] Added coming qualifiers in changelog
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
////
[DOCS] Adds changelog to Elasticsearch Reference (#30271)
2018-05-01 13:34:26 -04:00
[[release-notes-7.0.0]]
== {es} 7.0.0
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
2018-04-18 10:42:05 -04:00
[DOCS] Added coming qualifiers in changelog
2018-05-03 22:38:19 -04:00
coming[7.0.0]
[DOCS] Adds changelog to Elasticsearch Reference (#30271)
2018-05-01 13:34:26 -04:00
[float]
[[breaking-7.0.0]]
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
2018-04-18 10:42:05 -04:00
=== Breaking Changes
Remove bulk fallback for write thread pool (#29609) The name of the bulk thread pool was renamed to "write" with "bulk" as a fallback name. This change was made in 6.x for BWC reasons yet in 7.0.0 we are removing this fallback. This commit removes this fallback for the write thread pool.
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])
Packaging: Unmark systemd service file as a config file (#29004) Systemd overrides should happen through /etc/systemd/system, not directly editing the service file. This commit removes marking the service file as configuration for rpm and deb packages.
2018-05-02 12:48:49 -04:00
<<systemd-service-file-config, Systemd service file is no longer marked as configuration>> ({pull}29004[#29004])
Remove the suggest metric from stats APIs (#29635) This metric previously existed for backwards compatibility reasons although the suggest stats were folded into search stats. This metric was deprecated in 6.3.0 and this commit removes them for 7.0.0.
2018-04-24 19:03:48 -04:00
<<remove-suggest-metric, Removed `suggest` metric on stats APIs>> ({pull}29635[#29635])
In the field capabilities API, remove support for providing fields in the request body. (#30185)
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])
[DOCS] Removes X-Pack Elasticsearch release notes (#30272)
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>>.
Network: Remove http.enabled setting (#29601) This commit removes the http.enabled setting. While all real nodes (started with bin/elasticsearch) will always have an http binding, there are many tests that rely on the quickness of not actually needing to bind to 2 ports. For this case, the MockHttpTransport.TestPlugin provides a dummy http transport implementation which is used by default in ESIntegTestCase. closes #12792
2018-05-02 14:42:05 -04:00
* <<remove-http-enabled, Removed `http.enabled` setting>> ({pull}29601[#29601])
[DOCS] Added coming qualifiers in changelog
2018-05-03 22:38:19 -04:00
//[float]
//=== Breaking Java Changes
[DOCS] Commented out empty sections in the changelog to fix the doc build. (#30372)
2018-05-03 19:31:32 -04:00
[float]
Network: Remove http.enabled setting (#29601) This commit removes the http.enabled setting. While all real nodes (started with bin/elasticsearch) will always have an http binding, there are many tests that rely on the quickness of not actually needing to bind to 2 ports. For this case, the MockHttpTransport.TestPlugin provides a dummy http transport implementation which is used by default in ESIntegTestCase. closes #12792
2018-05-02 14:42:05 -04:00
=== Deprecations
[DOCS] Removes X-Pack Elasticsearch release notes (#30272)
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.
[DOCS] Adds changelog to Elasticsearch Reference (#30271)
2018-05-01 13:34:26 -04:00
//[float]
//=== New Features
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
2018-04-18 10:42:05 -04:00
[DOCS] Adds changelog to Elasticsearch Reference (#30271)
2018-05-01 13:34:26 -04:00
//[float]
//=== Enhancements
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
2018-04-18 10:42:05 -04:00
[DOCS] Adds changelog to Elasticsearch Reference (#30271)
2018-05-01 13:34:26 -04:00
[float]
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
2018-04-18 10:42:05 -04:00
=== Bug Fixes
Use date format in `date_range` mapping before fallback to default (#29310) If the date format is not forced in query, use the format in mapping before fallback to the default format. Closes #29282
2018-05-09 03:41:44 -04:00
Use date format in `date_range` mapping before fallback to default ({pull}29310[#29310])
Avoid NPE in `more_like_this` when field has zero tokens (#30365) Fixes and edge case when using `more_like_this` where TermVectorsWriter could throw an NPE when a field produced zero tokens after analysis. This changes the implementation to use an empty list of tokens in this case. Closes #30148
2018-05-08 09:13:07 -04:00
Fix NPE in 'more_like_this' when field has zero tokens ({pull}30365[#30365])
Added changelog entry for deb prerelease version change (#30184) This commit adds a changelog entry for the change in #29000.
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])
[Rollup] Validate timezone in range queries (#30338) When validating the search request, we make sure any date_histogram aggregations have timezones that match the jobs. But we didn't do any such validation on range queries. While it wouldn't produce incorrect results, it would be confusing to the user as no documents would match the aggregation (because we add a filter clause on the timezone for the agg). Now the user gets an exception up front, and some helpful text about why the range query didnt match, and which timezones are acceptable
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])
SQL: Fix parsing of dates with milliseconds (#30419) Dates internally contain milliseconds (which appear when converting them to Strings) however parsing does not accept them (and is being strict). The parser has been changed so that Date is mandatory but the time (including its fractions such as millis) are optional. Fix #30002
2018-05-10 13:14:54 -04:00
SQL::
* Fix parsing of Dates containing milliseconds ({pull}30419[#30419])
[DOCS] Commented out empty sections in the changelog to fix the doc build. (#30372)
2018-05-03 19:31:32 -04:00
[float]
Added changelog entry for deb prerelease version change (#30184) This commit adds a changelog entry for the change in #29000.
2018-05-02 12:00:35 -04:00
=== Regressions
Fail snapshot operations early on repository corruption (#30140) A NullPointerException is thrown when trying to create or delete a snapshot in a repository that has been written to by an older Elasticsearch after writing to it with a newer Elasticsearch version. This is because the way snapshots are formatted in the repository snapshots index file changed in #24477. This commit changes the parsing of the repository index file so that it now detects a corrupted index file and fails early the snapshot operation. closes #29052
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])
Fix NPE when CumulativeSum agg encounters null/empty bucket (#29641) Fix NPE when CumulativeSum agg encounters null/empty bucket If the cusum agg encounters a null value, it's because the value is missing (like the first value from a derivative agg), the path is not valid, or the bucket in the path was empty. Previously cusum would just explode on the null, but this changes it so we only increment the sum if the value is non-null and finite. This is safe because even if the cusum encounters all null or empty buckets, the cumulative sum is still zero (like how the sum agg returns zero even if all the docs were missing values) I went ahead and tweaked AggregatorTestCase to allow testing pipelines, so that I could delete the IT test and reimplement it as AggTests. Closes #27544
2018-05-02 15:22:55 -04:00
Fix NPE when CumulativeSum agg encounters null value/empty bucket ({pull}29641[#29641])
Do not fail snapshot when deleting a missing snapshotted file (#30332) When deleting or creating a snapshot for a given shard, elasticsearch usually starts by listing all the existing snapshotted files in the repository. Then it computes a diff and deletes the snapshotted files that are not needed anymore. During this deletion, an exception is thrown if the file to be deleted does not exist anymore. This behavior is challenging with cloud based repository implementations like S3 where a file that has been deleted can still appear in the bucket for few seconds/minutes (because the deletion can take some time to be fully replicated on S3). If the deleted file appears in the listing of files, then the following deletion will fail with a NoSuchFileException and the snapshot will be partially created/deleted. This pull request makes the deletion of these files a bit less strict, ie not failing if the file we want to delete does not exist anymore. It introduces a new BlobContainer.deleteIgnoringIfNotExists() method that can be used at some specific places where not failing when deleting a file is considered harmless. Closes #28322
2018-05-07 03:35:55 -04:00
Do not fail snapshot when deleting a missing snapshotted file ({pull}30332[#30332])
Fix NPE when CumulativeSum agg encounters null/empty bucket (#29641) Fix NPE when CumulativeSum agg encounters null/empty bucket If the cusum agg encounters a null value, it's because the value is missing (like the first value from a derivative agg), the path is not valid, or the bucket in the path was empty. Previously cusum would just explode on the null, but this changes it so we only increment the sum if the value is non-null and finite. This is safe because even if the cusum encounters all null or empty buckets, the cumulative sum is still zero (like how the sum agg returns zero even if all the docs were missing values) I went ahead and tweaked AggregatorTestCase to allow testing pipelines, so that I could delete the IT test and reimplement it as AggTests. Closes #27544
2018-05-02 15:22:55 -04:00
[DOCS] Added coming qualifiers in changelog
2018-05-03 22:38:19 -04:00
//[float]
//=== Regressions
[DOCS] Adds changelog to Elasticsearch Reference (#30271)
2018-05-01 13:34:26 -04:00
//[float]
//=== Known Issues
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
2018-04-18 10:42:05 -04:00
[DOCS] Adds changelog to Elasticsearch Reference (#30271)
2018-05-01 13:34:26 -04:00
[[release-notes-6.4.0]]
== {es} 6.4.0
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
2018-04-18 10:42:05 -04:00
[DOCS] Added coming qualifiers in changelog
2018-05-03 22:38:19 -04:00
coming[6.4.0]
//[float]
[[breaking-6.4.0]]
//=== Breaking Changes
//[float]
//=== Breaking Java Changes
Client: Deprecate many argument performRequest (#30315) Deprecate the many arguments versions of `performRequest` and `performRequestAsync` in favor of the `Request` object flavored variants introduced in #29623. We'll be dropping the many arguments variants in 7.0 because they make it difficult to add new features in a backwards compatible way and they create a *ton* of intellisense noise.
2018-05-08 14:38:55 -04:00
[float]
=== Deprecations
Deprecated multi-argument versions of the request methods in the RestClient.
Prefer the "Request" object flavored methods. ({pull}30315[#30315])
[DOCS] Added coming qualifiers in changelog
2018-05-03 22:38:19 -04:00
Add a new `_ignored` meta field. (#29658) This adds a new `_ignored` meta field which indexes and stores fields that have been ignored at index time because of the `ignore_malformed` option. It makes malformed documents easier to identify by using `exists` or `term(s)` queries on the `_ignored` field. Closes #29494
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])
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
2018-04-18 10:42:05 -04:00
Expose the Lucene Korean analyzer module in a plugin (#30397) This change adds a new plugin called `analysis-nori` that exposes Korean text analysis in es using the new Lucene Korean analyzer module named (`nori`). The plugin adds: * a Korean analyzer: `nori` * a Korean tokenizer: `nori_tokenizer` * a part of speech stop filter: `nori_part_of_speech` * a filter that can replace Hanja characters with their Hangul transcription: `nori_readingform`
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])
[DOCS] Adds changelog to Elasticsearch Reference (#30271)
2018-05-01 13:34:26 -04:00
[float]
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
2018-04-18 10:42:05 -04:00
=== Enhancements
Deprecate not copy settings and explicitly disallow (#30404) We want copying settings to be the default behavior. This commit deprecates not copying settings, and disallows explicitly not copying settings. This gives users a transition path to the future default behavior.
2018-05-13 10:30:05 -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], {pull}30404[#30404])
Adjust copy settings on resize BWC version This commit adjusts the BWC version for copy settings on resize operations after the behavior was backported to 6.x.
2018-05-01 08:46:12 -04:00
Client: Deprecate many argument performRequest (#30315) Deprecate the many arguments versions of `performRequest` and `performRequestAsync` in favor of the `Request` object flavored variants introduced in #29623. We'll be dropping the many arguments variants in 7.0 because they make it difficult to add new features in a backwards compatible way and they create a *ton* of intellisense noise.
2018-05-08 14:38:55 -04:00
Added new "Request" object flavored request methods in the RestClient. Prefer
these instead of the multi-argument versions. ({pull}29623[#29623])
REST Client: Add Request object flavored methods (#29623) Adds two new methods to `RestClient` that take a `Request` object. These methods will allows us to add more per-request customizable options without creating more and more and more overloads of the `performRequest` and `performRequestAsync` methods. These new methods look like: ``` Response performRequest(Request request) ``` and ``` void performRequestAsync(Request request, ResponseListener responseListener) ``` This change doesn't add any actual features but enables adding things like per request timeouts and per request node selectors. This change *does* rework the `HighLevelRestClient` and its tests to use these new `Request` objects and it does update the docs.
2018-05-01 14:31:23 -04:00
LLClient: Add setJsonEntity (#30447) Adds `Request#setJsonEntity(String)` which short circuits the process of sending a json string which is super common.
2018-05-09 18:33:03 -04:00
Added `setJsonEntity` to `Request` object so it is marginally easier to send JSON. ({pull}30447[#30447])
Watcher: Increase HttpClient parallel sent requests (#30130) The HTTPClient used in watcher is based on the apache http client. The current client is using a lot of defaults - which are not always optimal. Two of those defaults are the maximum number of total connections and the maximum number of connections to a single route. If one of those limits is reached, the HTTPClient waits for a connection to be finished thus acting in a blocking fashion. In order to prevent this when many requests are being executed, we increase the limit of total connections as well as the connections per route (a route is basically an endpoint, which also contains proxy information, not containing an URL, just hosts). On top of that an additional option has been set to evict long running connections, which can potentially be reused after some time. As this requires an additional background thread, this required some changes to ensure that the httpclient is closed properly. Also the timeout for this can be configured.
2018-05-09 03:37:47 -04:00
Watcher HTTP client used in watches now allows more parallel connections to the
same endpoint and evicts long running connections. ({pull}30130[#30130])
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])
REST Client: Add Request object flavored methods (#29623) Adds two new methods to `RestClient` that take a `Request` object. These methods will allows us to add more per-request customizable options without creating more and more and more overloads of the `performRequest` and `performRequestAsync` methods. These new methods look like: ``` Response performRequest(Request request) ``` and ``` void performRequestAsync(Request request, ResponseListener responseListener) ``` This change doesn't add any actual features but enables adding things like per request timeouts and per request node selectors. This change *does* rework the `HighLevelRestClient` and its tests to use these new `Request` objects and it does update the docs.
2018-05-01 14:31:23 -04:00
Add put index template api to high level rest client (#30400) Relates #27205
2018-05-06 09:47:36 -04:00
Added put index template API to the high level rest client ({pull}30400[#30400])
Add `coordinating_only` node selector (#30313) Today we can execute cluster API actions on only master, data or ingest nodes using the `master:true`, `data:true` and `ingest:true` filters, but it is not so easy to select coordinating-only nodes (i.e. those nodes that are neither master nor data nor ingest nodes). This change fixes this by adding support for a `coordinating_only` filter such that `coordinating_only:true` adds all coordinating-only nodes to the set of selected nodes, and `coordinating_only:false` deletes them. Resolves #28831.
2018-05-09 07:14:07 -04:00
Add ability to filter coordinating-only nodes when interacting with cluster
APIs. ({pull}30313[#30313])
[DOCS] Adds changelog to Elasticsearch Reference (#30271)
2018-05-01 13:34:26 -04:00
[float]
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
2018-04-18 10:42:05 -04:00
=== Bug Fixes
Use date format in `date_range` mapping before fallback to default (#29310) If the date format is not forced in query, use the format in mapping before fallback to the default format. Closes #29282
2018-05-09 03:41:44 -04:00
Use date format in `date_range` mapping before fallback to default ({pull}29310[#29310])
Avoid NPE in `more_like_this` when field has zero tokens (#30365) Fixes and edge case when using `more_like_this` where TermVectorsWriter could throw an NPE when a field produced zero tokens after analysis. This changes the implementation to use an empty list of tokens in this case. Closes #30148
2018-05-08 09:13:07 -04:00
Fix NPE in 'more_like_this' when field has zero tokens ({pull}30365[#30365])
Do not ignore request analysis/similarity on resize (#30216) Today when a resize operation is performed, we copy the analysis, similarity, and sort settings from the source index. It is possible for the resize request to include additional index settings including analysis, similarity, and sort settings. We reject sort settings when validating the request. However, we silently ignore analysis and similarity settings on the request that are already set on the source index. Since it is possible to change the analysis and similarity settings on an existing index, this should be considered a bug and the sort of leniency that we abhor. This commit addresses this bug by allowing the request analysis/similarity settings to override the existing analysis/similarity settings on the target.
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])
Fix NPE when CumulativeSum agg encounters null/empty bucket (#29641) Fix NPE when CumulativeSum agg encounters null/empty bucket If the cusum agg encounters a null value, it's because the value is missing (like the first value from a derivative agg), the path is not valid, or the bucket in the path was empty. Previously cusum would just explode on the null, but this changes it so we only increment the sum if the value is non-null and finite. This is safe because even if the cusum encounters all null or empty buckets, the cumulative sum is still zero (like how the sum agg returns zero even if all the docs were missing values) I went ahead and tweaked AggregatorTestCase to allow testing pipelines, so that I could delete the IT test and reimplement it as AggTests. Closes #27544
2018-05-02 15:22:55 -04:00
Fix NPE when CumulativeSum agg encounters null value/empty bucket ({pull}29641[#29641])
REST Client: Add Request object flavored methods (#29623) Adds two new methods to `RestClient` that take a `Request` object. These methods will allows us to add more per-request customizable options without creating more and more and more overloads of the `performRequest` and `performRequestAsync` methods. These new methods look like: ``` Response performRequest(Request request) ``` and ``` void performRequestAsync(Request request, ResponseListener responseListener) ``` This change doesn't add any actual features but enables adding things like per request timeouts and per request node selectors. This change *does* rework the `HighLevelRestClient` and its tests to use these new `Request` objects and it does update the docs.
2018-05-01 14:31:23 -04:00
[ML] Account for gaps in data counts after job is reopened (#30294) This commit fixes an issue with the data diagnostics were empty buckets are not reported even though they should. Once a job is reopened, the diagnostics do not get initialized from the current data counts (especially the latest record timestamp). The result is that if the data that is sent have a time gap compared to the previous ones, that gap is not accounted for in the empty bucket count. This commit fixes that by initializing the diagnostics with the current data counts. Closes #30080
2018-05-03 10:08:24 -04:00
Machine Learning::
* Account for gaps in data counts after job is reopened ({pull}30294[#30294])
Add stricter geohash parsing (#30376) Adds verification that geohashes are not empty and contain only valid characters. It fixes the issue when en empty geohash is treated as [-180, -90] and geohashes with non-geohash character are getting resolved into invalid coordinates. Closes #23579
2018-05-07 13:56:39 -04:00
Add validation that geohashes are not empty and don't contain unsupported characters ({pull}30376[#30376])
[Rollup] Validate timezone in range queries (#30338) When validating the search request, we make sure any date_histogram aggregations have timezones that match the jobs. But we didn't do any such validation on range queries. While it wouldn't produce incorrect results, it would be confusing to the user as no documents would match the aggregation (because we add a filter clause on the timezone for the agg). Now the user gets an exception up front, and some helpful text about why the range query didnt match, and which timezones are acceptable
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])
SQL: Fix parsing of dates with milliseconds (#30419) Dates internally contain milliseconds (which appear when converting them to Strings) however parsing does not accept them (and is being strict). The parser has been changed so that Date is mandatory but the time (including its fractions such as millis) are optional. Fix #30002
2018-05-10 13:14:54 -04:00
SQL::
* Fix parsing of Dates containing milliseconds ({pull}30419[#30419])
Auto-expand replicas when adding or removing nodes (#30423) Auto-expands replicas in the same cluster state update (instead of a follow-up reroute) where nodes are added or removed. Closes #1873, fixing an issue where nodes drop their copy of auto-expanded data when coming up, only to sync it again later.
2018-05-07 16:26:31 -04:00
Allocation::
Auto-expand replicas when adding or removing nodes to prevent shard copies from
being dropped and resynced when a data node rejoins the cluster ({pull}30423[#30423])
[DOCS] Commented out empty sections in the changelog to fix the doc build. (#30372)
2018-05-03 19:31:32 -04:00
//[float]
//=== Regressions
//[float]
//=== Known Issues
[DOCS] Added coming qualifiers in changelog
2018-05-03 22:38:19 -04:00
[[release-notes-6.3.1]]
== Elasticsearch version 6.3.1
[DOCS] Commented out empty sections in the changelog to fix the doc build. (#30372)
2018-05-03 19:31:32 -04:00
[DOCS] Added coming qualifiers in changelog
2018-05-03 22:38:19 -04:00
coming[6.3.1]
[DOCS] Commented out empty sections in the changelog to fix the doc build. (#30372)
2018-05-03 19:31:32 -04:00
//[float]
[DOCS] Added coming qualifiers in changelog
2018-05-03 22:38:19 -04:00
[[breaking-6.3.1]]
[DOCS] Commented out empty sections in the changelog to fix the doc build. (#30372)
2018-05-03 19:31:32 -04:00
//=== Breaking Changes
//[float]
//=== Breaking Java Changes
//[float]
//=== Deprecations
//[float]
//=== New Features
//[float]
//=== Enhancements
[DOCS] Added coming qualifiers in changelog
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])
Security: reduce garbage during index resolution (#30180) The IndexAndAliasesResolver resolves the indices and aliases for each request and also handles local and remote indices. The current implementation uses the ResolvedIndices class to hold the resolved indices and aliases. While evaluating the indices and aliases against the user's permissions, the final value for ResolvedIndices is constructed. Prior to this change, this was done by creating a ResolvedIndices for the first set of indices and for each additional addition, a new ResolvedIndices object is created and merged with the existing one. With a small number of indices and aliases this does not pose a large problem; however as the number of indices/aliases grows more list allocations and array copies are needed resulting in a large amount of garbage and severely impacted performance. This change introduces a builder for ResolvedIndices that appends to mutable lists until the final value has been constructed, which will ultimately reduce the amount of garbage generated by this code.
2018-05-03 14:48:23 -04:00
Move respect accept header on no handler to 6.3.1 This commit moves the changelog entry for the change to respect the accept header on no handler from the 7.0.0 section of the docs to 6.3.1.
2018-05-04 20:50:30 -04:00
Respect accept header on requests with no handler ({pull}30383[#30383])
SQL: Fix parsing of dates with milliseconds (#30419) Dates internally contain milliseconds (which appear when converting them to Strings) however parsing does not accept them (and is being strict). The parser has been changed so that Date is mandatory but the time (including its fractions such as millis) are optional. Fix #30002
2018-05-10 13:14:54 -04:00
SQL::
* Fix parsing of Dates containing milliseconds ({pull}30419[#30419])
[DOCS] Adds changelog to Elasticsearch Reference (#30271)
2018-05-01 13:34:26 -04:00
//[float]
//=== Regressions
Add a CHANGELOG file for release notes. (#29450) * Add a CHANGELOG file for 7.x release notes. * update file to include 6.x * remove confusing comment and small edit to section title * moving CHANGELOG file under docs directory, as it pertains to release notes.
2018-04-18 10:42:05 -04:00
[DOCS] Adds changelog to Elasticsearch Reference (#30271)
2018-05-01 13:34:26 -04:00
//[float]
//=== Known Issues