|
|
@@ -28,13 +28,40 @@ Other versions:
|
|
|
|
|
|
endif::[]
|
|
|
|
|
|
-// The notable-highlights tag marks entries that
|
|
|
-// should be featured in the Stack Installation and Upgrade Guide:
|
|
|
// tag::notable-highlights[]
|
|
|
-// [discrete]
|
|
|
-// === Heading
|
|
|
-//
|
|
|
-// Description.
|
|
|
+
|
|
|
+[discrete]
|
|
|
+[[improve_storage_efficiency_for_non_metric_fields_in_tsdb]]
|
|
|
+=== Improve storage efficiency for non-metric fields in TSDB
|
|
|
+Adds a new `doc_values` encoding for non-metric fields in TSDB that takes advantage of TSDB's index sorting.
|
|
|
+While terms that are used in multiple documents (such as the host name) are already stored only once in the terms dictionary,
|
|
|
+there are a lot of repetitions in the references to the terms dictionary that are stored in `doc_values` (ordinals).
|
|
|
+In TSDB, documents (and therefore `doc_values`) are implicitly sorted by dimenstions and timestamp.
|
|
|
+This means that for each time series, we are storing long consecutive runs of the same ordinal.
|
|
|
+With this change, we are introducing an encoding that detects and efficiently stores runs of the same value (such as `1 1 1 2 2 2 …`),
|
|
|
+and runs of cycling values (such as `1 2 1 2 …`).
|
|
|
+In our testing, we have seen a reduction in storage size by about 13%.
|
|
|
+The effectiveness of this encoding depends on how many non-metric fields, such as dimensions, are used.
|
|
|
+The more non-metric fields, the more effective this improvement will be.
|
|
|
+
|
|
|
+{es-pull}99747[#99747]
|
|
|
+
|
|
|
+[discrete]
|
|
|
+[[ga_release_of_synonyms_api]]
|
|
|
+=== GA Release of Synonyms API
|
|
|
+Removes the beta label for the Synonyms API to make it GA.
|
|
|
+
|
|
|
+{es-pull}103223[#103223]
|
|
|
+
|
|
|
+[discrete]
|
|
|
+[[flag_in_field_caps_to_return_only_fields_with_values_in_index]]
|
|
|
+=== Flag in `_field_caps` to return only fields with values in index
|
|
|
+We added support for filtering the field capabilities API output by removing
|
|
|
+fields that don't have a value. This can be done through the newly added
|
|
|
+`include_empty_fields` parameter, which defaults to true.
|
|
|
+
|
|
|
+{es-pull}103651[#103651]
|
|
|
+
|
|
|
// end::notable-highlights[]
|
|
|
|
|
|
|
elasticsearchmachine