honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/docs/reference/release-notes/7.0.0-alpha1.asciidoc

30 lines
1.1 KiB
Plaintext
Raw Normal View History

Migrate migration docs from 6.0 to 7.0 (#26227) * Migrate migration docs from 6.0 to 7.0 Since we only keep one version of migration docs and master is now on 7.0, we should migrate these so breaking changes can be added in the right place. * Remove release notes as well They link to the migration guides, so they have to go. * Add placeholder notes for 7.0 so doc build is happy
2017-08-16 15:12:44 -04:00
[[release-notes-7.0.0-alpha1]]
== 7.0.0-alpha1 Release Notes
The changes listed below have been released for the first time in Elasticsearch 7.0.0-alpha1.
[[breaking-7.0.0-alpha1]]
[float]
=== Breaking changes
Remove tribe node support (#28443) Tribe node has been superseeded by Cross-Cluster-Search. This change removes the tribe node support entirely.
2018-01-30 14:40:19 -05:00
Core::
REST: Remove GET support for clear cache indices (#29525) Clearing the cache indices can be done via GET and POST. As GET should only support read only operations, this removes the support for using GET for clearing the indices caches.
2018-04-27 02:41:36 -04:00
* Tribe node has been removed in favor of Cross-Cluster-Search
CCS: Drop http address from remote cluster info (#29568) They are expensive to fetch and no longer needed by Kibana so they *shouldn't* be needed by anyone else either. Closes #29207
2018-04-27 14:19:00 -04:00
Cross-Cluster-Search::
* `http_addresses` has been removed from the <<cluster-remote-info>> API
because it is expensive to fetch and no longer needed by Kibana.
REST: Remove GET support for clear cache indices (#29525) Clearing the cache indices can be done via GET and POST. As GET should only support read only operations, this removes the support for using GET for clearing the indices caches.
2018-04-27 02:41:36 -04:00
Rest API::
* The Clear Cache API only supports `POST` as HTTP method
Percentile/Ranks should return null instead of NaN when empty (#30460) The other metric aggregations (min/max/etc) return `null` as their XContent value and string when nothing was computed (due to empty/missing fields). Percentiles and Percentile Ranks, however, return `NaN `which is inconsistent and confusing for the user. This fixes the inconsistency by making the aggs return `null`. This applies to both the numeric value and the "as string" value. Note: like the metric aggs, this does not change the value if fetched directly from the percentiles object, which will return as `NaN`/`"NaN"`. This only changes the XContent output. While this is a bugfix, it still breaks bwc in a minor way as the response changes from prior version. Closes #29066
2018-06-18 10:01:28 -04:00
Aggregations::
* The Percentiles and PercentileRanks aggregations now return `null` in the REST response,
instead of `NaN`. This makes it consistent with the rest of the aggregations. Note:
this only applies to the REST response, the java objects continue to return `NaN` (also
serialize suggestion responses as named writeables (#30284) Suggestion responses were previously serialized as streamables which made writing suggesters in plugins with custom suggestion response types impossible. This commit makes them serialized as named writeables and provides a facility for registering a reader for suggestion responses when registering a suggester. This also makes Suggestion responses abstract, requiring a suggester implementation to provide its own types. Suggesters which do not need anything additional to what is defined in Suggest.Suggestion should provide a minimal subclass. The existing plugin suggester integration tests are removed and replaced with an equivalent implementation as an example plugin.
2018-08-07 16:31:00 -04:00
consistent with other aggregations)
Suggesters::
* Plugins that register suggesters can now define their own types of suggestions and must
explicitly indicate the type of suggestion that they produce. Existing plugins will
require changes to their plugin registration. See the `custom-suggester` example
plugin {pull}30284[#30284]