root
/
elasticsearch
mirror of https://github.com/elastic/elasticsearch.git
1
0
Fork 0
Code Issues Actions 1 Packages Projects Releases Wiki Activity
elasticsearch/docs/reference/release-notes/8.0.0-alpha1.asciidoc

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

45 lines
1.9 KiB
Plaintext
Raw Normal View History

[DOCS] Adds placeholders for v8 highlights, breaking changes, release notes (#38641)
2019-02-09 07:48:42 +08:00
[[release-notes-8.0.0-alpha1]]
== {es} version 8.0.0-alpha1
[DOCS] Reformat release highlights as What's new. (#58074) * [DOCS] Reformat release highlights as What's new. * Removed line break.
2020-06-16 04:26:30 +08:00
coming[8.0.0]
[DOCS] Adds placeholders for v8 highlights, breaking changes, release notes (#38641)
2019-02-09 07:48:42 +08:00
The changes listed below have been released for the first time in {es}
8.0.0-alpha1.
Percentiles aggregation: disallow specifying same percentile v… (#52257) Disallow specifying the same percentile multiple times in percentiles aggregation Related: #51871
2020-02-26 20:40:33 +08:00
[[breaking-8.0.0-alpha1]]
[DOCS] Swap `[float]` for `[discrete]` (#60124) Changes instances of `[float]` in our docs for `[discrete]`. Asciidoctor prefers the `[discrete]` tag for floating headings: https://asciidoctor.org/docs/asciidoc-asciidoctor-diffs/#blocks
2020-07-23 23:48:22 +08:00
[discrete]
Percentiles aggregation: disallow specifying same percentile v… (#52257) Disallow specifying the same percentile multiple times in percentiles aggregation Related: #51871
2020-02-26 20:40:33 +08:00
=== Breaking changes
Aggregations::
[DOCS] Updates pull and issue release attributes (#58348)
2020-06-19 03:38:49 +08:00
* Disallow specifying the same percentile multiple times in percentiles aggregation {es-pull}52257[#52257]
[DOCS] Adds placeholders for v8 highlights, breaking changes, release notes (#38641)
2019-02-09 07:48:42 +08:00
Add validation for dynamic templates (#51233) Tries to load a `Mapper` instance for the mapping snippet of a dynamic template. This should catch things like using an analyzer that is undefined or mapping attributes that are unused. This is best effort: * If `{{name}}` placeholder is used in the mapping snippet then validation is skipped. * If `match_mapping_type` is not specified then validation is performed for all mapping types. If parsing succeeds with a single mapping type then this the dynamic mapping is considered valid. If is detected that a dynamic template mapping snippet is invalid at mapping update time then the mapping update is failed for indices created on 8.0.0-alpha1 and later. For indices created on prior version a deprecation warning is omitted instead. In 7.x clusters the mapping update will never fail in case of an invalid dynamic template mapping snippet and a deprecation warning will always be omitted. Closes #17411 Closes #24419 Co-authored-by: Adrien Grand <jpountz@gmail.com>
2020-02-27 18:52:27 +08:00
Mapping::
* Dynamic mappings in indices created on 8.0 and later have stricter validation at mapping update time.
[DOCS] Updates pull and issue release attributes (#58348)
2020-06-19 03:38:49 +08:00
(e.g. incorrect analyzer settings or unknown field types). {es-pull}51233[#51233]
Add validation for dynamic templates (#51233) Tries to load a `Mapper` instance for the mapping snippet of a dynamic template. This should catch things like using an analyzer that is undefined or mapping attributes that are unused. This is best effort: * If `{{name}}` placeholder is used in the mapping snippet then validation is skipped. * If `match_mapping_type` is not specified then validation is performed for all mapping types. If parsing succeeds with a single mapping type then this the dynamic mapping is considered valid. If is detected that a dynamic template mapping snippet is invalid at mapping update time then the mapping update is failed for indices created on 8.0.0-alpha1 and later. For indices created on prior version a deprecation warning is omitted instead. In 7.x clusters the mapping update will never fail in case of an invalid dynamic template mapping snippet and a deprecation warning will always be omitted. Closes #17411 Closes #24419 Co-authored-by: Adrien Grand <jpountz@gmail.com>
2020-02-27 18:52:27 +08:00
Add missing update by query breaking change entry (#59586) This should have been added with #59507
2020-07-16 03:06:47 +08:00
Update by query::
* Unsupported fields provided as part of the script section of the update by query API are now rejected.
Remove deprecated endpoints of hot threads API (#55109) This removes deprecated endpoints in hot threads action. Closes #52640
2020-04-15 03:36:57 +08:00
Deprecations::
[DOCS] Updates pull and issue release attributes (#58348)
2020-06-19 03:38:49 +08:00
* Remove undocumented endpoints of hot threads API {es-pull}55109[#55109]
Remove deprecated endpoints of hot threads API (#55109) This removes deprecated endpoints in hot threads action. Closes #52640
2020-04-15 03:36:57 +08:00
Remove slowlog level (#57591) Setting a slow log level requires an unnecessary conditional logic in SearchSlowLog and IndexingSlowLog The behaviour of setting a level on a slow logger can be achieved with correct slow log threshold settings. This PR is removing slow log and modifies tests to achieve the same behaviour with changing threshold. relates #56171
2020-06-04 19:33:28 +08:00
Slow loggers::
* `index.indexing.slowlog.level` and `index.search.slowlog.level` are removed. These settings can be worked around
by using appropriate thresholds. If for instance we want to simulate `index.indexing.slowlog.level` = `INFO` then
all we need to do is to set `index.indexing.slowlog.threshold.index.debug` and
[DOCS] Updates pull and issue release attributes (#58348)
2020-06-19 03:38:49 +08:00
`index.indexing.slowlog.threshold.index.trace` to `-1` {es-pull}57591[#57591]
Remove slowlog level (#57591) Setting a slow log level requires an unnecessary conditional logic in SearchSlowLog and IndexingSlowLog The behaviour of setting a level on a slow logger can be achieved with correct slow log threshold settings. This PR is removing slow log and modifies tests to achieve the same behaviour with changing threshold. relates #56171
2020-06-04 19:33:28 +08:00
Fix range query on date fields for number inputs (#63692) Currently, if you write a date range query with numeric 'to' or 'from' bounds, they can be interpreted as years if no format is provided. We use "strict_date_optional_time||epoch_millis" in this case that can interpret inputs like 1000 as the year 1000 for example. This PR change this to always interpret and parse numbers with the "epoch_millis" parser if no other formatter was provided. Closes #63680
2020-12-02 01:49:50 +08:00
Search::
* Consistent treatment of numeric values for range query on date fields without `format` {es-pull}[#63692]
[DOCS] Reformat release highlights as What's new. (#58074) * [DOCS] Reformat release highlights as What's new. * Removed line break.
2020-06-16 04:26:30 +08:00
[DOCS] Adds ml-cpp PRs to release notes (#75703)
2021-07-27 04:22:11 +08:00
[[enhancement-8.0.0-alpha1]]
[float]
=== Enhancements
Machine learning::
* The Windows build platform for the {ml} C++ code now uses Visual Studio 2019 {ml-pull}1352[#1352]
* The macOS build platform for the {ml} C++ code is now Mojave running Xcode 11.3.1,
or Ubuntu 20.04 running clang 8 for cross compilation {ml-pull}1429[#1429]
* The Linux build platform for the {ml} C++ code is now CentOS 7 running gcc 9.3 {ml-pull}1170[#1170]
* Add a new application for evaluating PyTorch models. The app depends on LibTorch - the C++ front end to PyTorch and performs inference on models stored in the TorchScript format {ml-pull}1902[#1902]