elasticsearch/docs/reference/release-notes/highlights.asciidoc
2024-04-08 17:45:22 +02:00

51 lines
1.8 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.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]
[[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:
- `default_retention` is applied to all data streams managed by the data stream lifecycle that do not have retention
defined on the data stream level.
- `max_retention` 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.
Furthermore, we introduce the term `effective_retention` which is the retention applied at a certain moment to a data
stream considering all the available retention configurations.
{es-pull}105682[#105682]
// end::notable-highlights[]