From 0418eb35a7db38280d180a6012c1f100cf54d1e4 Mon Sep 17 00:00:00 2001 From: Adrien Grand Date: Wed, 24 Jul 2019 15:05:23 +0200 Subject: [PATCH] Add 7.3 release highlights. (#44153) Add 7.3 release highlights. --- .../release-notes/highlights-7.3.0.asciidoc | 159 ++++++++++++++++++ .../release-notes/highlights.asciidoc | 4 +- 2 files changed, 162 insertions(+), 1 deletion(-) create mode 100644 docs/reference/release-notes/highlights-7.3.0.asciidoc diff --git a/docs/reference/release-notes/highlights-7.3.0.asciidoc b/docs/reference/release-notes/highlights-7.3.0.asciidoc new file mode 100644 index 00000000000..33002224a21 --- /dev/null +++ b/docs/reference/release-notes/highlights-7.3.0.asciidoc @@ -0,0 +1,159 @@ +[[release-highlights-7.3.0]] +== 7.3.0 release highlights +++++ +7.3.0 +++++ + +coming[7.3.0] + +//NOTE: The notable-highlights tagged regions are re-used in the +//Installation and Upgrade Guide + +// tag::notable-highlights[] +[float] +==== Voting-only master nodes + +A new <> role has been introduced that +allows nodes to participate in elections even though they are not eligible to become the master. +The benefit is that these nodes still help with high availability while +requiring less CPU and heap than master nodes. + +NOTE: The `node.voting-only` role is only available with the default +distribution of {es}. + +// end::notable-highlights[] + +// tag::notable-highlights[] +[float] +==== Reloading of search-time synonyms + +A new <> allows to reload the +definition of search-time analyzers and their associated resources. A common +use-case for this API is the reloading of search-time synonyms. In earlier +versions of Elasticsearch, users could force synonyms to be reloaded by closing +the index and then opening it again. With this new API, synonyms can be updated +without closing the index. + +NOTE: The Analyzer reload API is only available with the default distribution +of {es}. + +// end::notable-highlights[] + +// tag::notable-highlights[] +[float] +==== New `flattened` field type + +A new <> field type has been added, which can index +arbitrary `json` objects into a single field. This helps avoid hitting issues +due to many fields in mappings, at the cost of more limited search +functionality. + +NOTE: The <> field type is only available with the +default distribution of {es}. + +// end::notable-highlights[] + +// tag::notable-highlights[] +[float] +==== Functions on vector fields + +Painless now support computing the <> and +the <> of a query vector and either values of a +<> or <> field. + +NOTE: These functions are only available with the default distribution of {es}. + +// end::notable-highlights[] + +// tag::notable-highlights[] +[float] +==== Prefix and wildcard support for intervals + +<> now support querying by +<> or <>. + +// end::notable-highlights[] + +// tag::notable-highlights[] +[float] +==== Rare terms aggregation + +A new +<> +allows to find the least frequent values in a field. It is intended to replace +the `"order" : { "_count" : "asc" }` option of the +<>. + +// end::notable-highlights[] + +// tag::notable-highlights[] +[float] +==== Aliases are replicated via {ccr} + +Read aliases are now replicated via <>. Note that write +aliases are still not replicated since they only make sense for indices that +are being written to while follower indices do not receive direct writes. + +// end::notable-highlights[] + +// tag::notable-highlights[] +[float] +==== SQL supports frozen indices + +{es-sql} now supports querying <> via the new +<> keyword. + +// end::notable-highlights[] + +// tag::notable-highlights[] +[float] +==== Fixed memory leak when using templates in document-level security + +{xpack-ref}/document-level-security.html[Document-level security] was using an +unbounded cache for the set of visible documents. This could lead to a memory +leak when using a templated query as a role query. The cache has been fixed to +evict based on memory usage and has a limit of 50MB. + +// end::notable-highlights[] + +// tag::notable-highlights[] +[float] +==== More memory-efficient aggregations on `keyword` fields + +<> generally +need to build +<> +in order to run. Unfortunately this operation became more memory-intensive in +6.0 due to the move to doc-value iterators in order to improve handling of +sparse fields. Memory pressure of global ordinals now goes back to a more +similar level as what you could have on pre-6.0 releases. + +// end::notable-highlights[] + +// tag::notable-highlights[] +[float] +==== Data frame pivot transforms to create entity-centric indexes + +<>, released in 7.2, allow to transform an +existing index to a secondary, summarized index. 7.3 now introduces Data frame +pivot transforms in order to create entity-centric indexes that can summarize +the behavior of an entity.  + +NOTE: Data frames are only available with the default distribution of {es}. + +// end::notable-highlights[] + +// tag::notable-highlights[] +[float] +==== Outlier detection + +{stack-ov}/security-privileges.html[Outlier detection] utilizes Elastic data +frame indexes to evaluate source indexes across multiple dimensions and identify +clusters of data based on the assigned values and which values are different +from those of the clustered data point. An outlier score can be used to indicate +how different an entity is from other entities in the index based on the +dimensions that you supply. + +NOTE: Outlier detection requires a platinum license. + +// end::notable-highlights[] diff --git a/docs/reference/release-notes/highlights.asciidoc b/docs/reference/release-notes/highlights.asciidoc index de4ed91d862..1b48c8118c6 100644 --- a/docs/reference/release-notes/highlights.asciidoc +++ b/docs/reference/release-notes/highlights.asciidoc @@ -6,12 +6,14 @@ This section summarizes the most important changes in each release. For the full list, see <> and <>. +* <> * <> * <> * <> -- +include::highlights-7.3.0.asciidoc[] include::highlights-7.2.0.asciidoc[] include::highlights-7.1.0.asciidoc[] -include::highlights-7.0.0.asciidoc[] \ No newline at end of file +include::highlights-7.0.0.asciidoc[]