mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-29 01:44:36 -04:00
87 lines
3 KiB
Text
87 lines
3 KiB
Text
[[release-highlights]]
|
|
== What's new in {minor-version}
|
|
|
|
coming::[{minor-version}]
|
|
|
|
Here are the highlights of what's new and improved in {es} {minor-version}!
|
|
ifeval::["{release-state}"!="unreleased"]
|
|
For detailed information about this release, see the <<es-release-notes>> and
|
|
<<breaking-changes>>.
|
|
|
|
// Add previous release to the list
|
|
Other versions:
|
|
|
|
{ref-bare}/8.15/release-highlights.html[8.15]
|
|
| {ref-bare}/8.14/release-highlights.html[8.14]
|
|
| {ref-bare}/8.13/release-highlights.html[8.13]
|
|
| {ref-bare}/8.12/release-highlights.html[8.12]
|
|
| {ref-bare}/8.11/release-highlights.html[8.11]
|
|
| {ref-bare}/8.10/release-highlights.html[8.10]
|
|
| {ref-bare}/8.9/release-highlights.html[8.9]
|
|
| {ref-bare}/8.8/release-highlights.html[8.8]
|
|
| {ref-bare}/8.7/release-highlights.html[8.7]
|
|
| {ref-bare}/8.6/release-highlights.html[8.6]
|
|
| {ref-bare}/8.5/release-highlights.html[8.5]
|
|
| {ref-bare}/8.4/release-highlights.html[8.4]
|
|
| {ref-bare}/8.3/release-highlights.html[8.3]
|
|
| {ref-bare}/8.2/release-highlights.html[8.2]
|
|
| {ref-bare}/8.1/release-highlights.html[8.1]
|
|
| {ref-bare}/8.0/release-highlights.html[8.0]
|
|
|
|
endif::[]
|
|
|
|
// tag::notable-highlights[]
|
|
|
|
[discrete]
|
|
[[esql_inlinestats]]
|
|
=== ESQL: INLINESTATS
|
|
This adds the `INLINESTATS` command to ESQL which performs a STATS and
|
|
then enriches the results into the output stream. So, this query:
|
|
|
|
[source,esql]
|
|
----
|
|
FROM test
|
|
| INLINESTATS m=MAX(a * b) BY b
|
|
| WHERE m == a * b
|
|
| SORT a DESC, b DESC
|
|
| LIMIT 3
|
|
----
|
|
|
|
Produces output like:
|
|
|
|
| a | b | m |
|
|
| --- | --- | ----- |
|
|
| 99 | 999 | 98901 |
|
|
| 99 | 998 | 98802 |
|
|
| 99 | 997 | 98703 |
|
|
|
|
{es-pull}109583[#109583]
|
|
|
|
[discrete]
|
|
[[always_allow_rebalancing_by_default]]
|
|
=== Always allow rebalancing by default
|
|
In earlier versions of {es} the `cluster.routing.allocation.allow_rebalance` setting defaults to
|
|
`indices_all_active` which blocks all rebalancing moves while the cluster is in `yellow` or `red` health. This was
|
|
appropriate for the legacy allocator which might do too many rebalancing moves otherwise. Today's allocator has
|
|
better support for rebalancing a cluster that is not in `green` health, and expects to be able to rebalance some
|
|
shards away from over-full nodes to avoid allocating shards to undesirable locations in the first place. From
|
|
version 8.16 `allow_rebalance` setting defaults to `always` unless the legacy allocator is explicitly enabled.
|
|
|
|
{es-pull}111015[#111015]
|
|
|
|
[discrete]
|
|
[[add_global_retention_in_data_stream_lifecycle]]
|
|
=== Add global retention in data stream lifecycle
|
|
Data stream lifecycle now supports configuring retention on a cluster level, namely global retention. Global retention
|
|
allows us to configure two different retentions:
|
|
|
|
- `data_streams.lifecycle.retention.default` is applied to all data streams managed by the data stream lifecycle that do not have retention
|
|
defined on the data stream level.
|
|
- `data_streams.lifecycle.retention.max` is applied to all data streams managed by the data stream lifecycle and it allows any data stream
|
|
data to be deleted after the `max_retention` has passed.
|
|
|
|
{es-pull}111972[#111972]
|
|
|
|
// end::notable-highlights[]
|
|
|
|
|