|
| 1 | +[[release-highlights-7.3.0]] |
| 2 | +== 7.3.0 release highlights |
| 3 | +++++ |
| 4 | +<titleabbrev>7.3.0</titleabbrev> |
| 5 | +++++ |
| 6 | + |
| 7 | +coming[7.3.0] |
| 8 | + |
| 9 | +//NOTE: The notable-highlights tagged regions are re-used in the |
| 10 | +//Installation and Upgrade Guide |
| 11 | + |
| 12 | +// tag::notable-highlights[] |
| 13 | +[float] |
| 14 | +==== Voting-only master nodes |
| 15 | + |
| 16 | +A new <<voting-only-node,`node.voting-only`>> role has been introduced that |
| 17 | +allows nodes to participate in elections even though they are not eligible to become the master. |
| 18 | +The benefit is that these nodes still help with high availability while |
| 19 | +requiring less CPU and heap than master nodes. |
| 20 | + |
| 21 | +NOTE: The `node.voting-only` role is only available with the default |
| 22 | +distribution of {es}. |
| 23 | + |
| 24 | +// end::notable-highlights[] |
| 25 | + |
| 26 | +// tag::notable-highlights[] |
| 27 | +[float] |
| 28 | +==== Reloading of search-time synonyms |
| 29 | + |
| 30 | +A new <<indices-reload-analyzers,Analyzer reload API>> allows to reload the |
| 31 | +definition of search-time analyzers and their associated resources. A common |
| 32 | +use-case for this API is the reloading of search-time synonyms. In earlier |
| 33 | +versions of Elasticsearch, users could force synonyms to be reloaded by closing |
| 34 | +the index and then opening it again. With this new API, synonyms can be updated |
| 35 | +without closing the index. |
| 36 | + |
| 37 | +NOTE: The Analyzer reload API is only available with the default distribution |
| 38 | +of {es}. |
| 39 | + |
| 40 | +// end::notable-highlights[] |
| 41 | + |
| 42 | +// tag::notable-highlights[] |
| 43 | +[float] |
| 44 | +==== New `flattened` field type |
| 45 | + |
| 46 | +A new <<flattened,`flattened`>> field type has been added, which can index |
| 47 | +arbitrary `json` objects into a single field. This helps avoid hitting issues |
| 48 | +due to many fields in mappings, at the cost of more limited search |
| 49 | +functionality. |
| 50 | + |
| 51 | +NOTE: The <<flattened,`flattened`>> field type is only available with the |
| 52 | +default distribution of {es}. |
| 53 | + |
| 54 | +// end::notable-highlights[] |
| 55 | + |
| 56 | +// tag::notable-highlights[] |
| 57 | +[float] |
| 58 | +==== Functions on vector fields |
| 59 | + |
| 60 | +Painless now support computing the <<vector-functions,cosine similarity>> and |
| 61 | +the <<vector-functions,dot product>> of a query vector and either values of a |
| 62 | +<<sparse-vector,`sparse_vector`>> or <<dense-vector,`dense_vector`>> field. |
| 63 | + |
| 64 | +NOTE: These functions are only available with the default distribution of {es}. |
| 65 | + |
| 66 | +// end::notable-highlights[] |
| 67 | + |
| 68 | +// tag::notable-highlights[] |
| 69 | +[float] |
| 70 | +==== Prefix and wildcard support for intervals |
| 71 | + |
| 72 | +<<query-dsl-intervals-query,Intervals>> now support querying by |
| 73 | +<<intervals-prefix,prefix>> or <<intervals-wildcard,wildcard>>. |
| 74 | + |
| 75 | +// end::notable-highlights[] |
| 76 | + |
| 77 | +// tag::notable-highlights[] |
| 78 | +[float] |
| 79 | +==== Rare terms aggregation |
| 80 | + |
| 81 | +A new |
| 82 | +<<search-aggregations-bucket-rare-terms-aggregation,Rare Terms aggregation>> |
| 83 | +allows to find the least frequent values in a field. It is intended to replace |
| 84 | +the `"order" : { "_count" : "asc" }` option of the |
| 85 | +<<search-aggregations-bucket-terms-aggregation,terms aggregations>>. |
| 86 | + |
| 87 | +// end::notable-highlights[] |
| 88 | + |
| 89 | +// tag::notable-highlights[] |
| 90 | +[float] |
| 91 | +==== Aliases are replicated via {ccr} |
| 92 | + |
| 93 | +Read aliases are now replicated via <<ccr-put-follow,{ccr}>>. Note that write |
| 94 | +aliases are still not replicated since they only make sense for indices that |
| 95 | +are being written to while follower indices do not receive direct writes. |
| 96 | + |
| 97 | +// end::notable-highlights[] |
| 98 | + |
| 99 | +// tag::notable-highlights[] |
| 100 | +[float] |
| 101 | +==== SQL supports frozen indices |
| 102 | + |
| 103 | +{es-sql} now supports querying <<frozen-indices, frozen indices>> via the new |
| 104 | +<<sql-index-frozen,`FROZEN`>> keyword. |
| 105 | + |
| 106 | +// end::notable-highlights[] |
| 107 | + |
| 108 | +// tag::notable-highlights[] |
| 109 | +[float] |
| 110 | +==== Fixed memory leak when using templates in document-level security |
| 111 | + |
| 112 | +{xpack-ref}/document-level-security.html[Document-level security] was using an |
| 113 | +unbounded cache for the set of visible documents. This could lead to a memory |
| 114 | +leak when using a templated query as a role query. The cache has been fixed to |
| 115 | +evict based on memory usage and has a limit of 50MB. |
| 116 | + |
| 117 | +// end::notable-highlights[] |
| 118 | + |
| 119 | +// tag::notable-highlights[] |
| 120 | +[float] |
| 121 | +==== More memory-efficient aggregations on `keyword` fields |
| 122 | + |
| 123 | +<<search-aggregations-bucket-terms-aggregation,Terms aggregations>> generally |
| 124 | +need to build |
| 125 | +<<search-aggregations-bucket-terms-aggregation-execution-hint,global ordinals>> |
| 126 | +in order to run. Unfortunately this operation became more memory-intensive in |
| 127 | +6.0 due to the move to doc-value iterators in order to improve handling of |
| 128 | +sparse fields. Memory pressure of global ordinals now goes back to a more |
| 129 | +similar level as what you could have on pre-6.0 releases. |
| 130 | + |
| 131 | +// end::notable-highlights[] |
| 132 | + |
| 133 | +// tag::notable-highlights[] |
| 134 | +[float] |
| 135 | +==== Data frame pivot transforms to create entity-centric indexes |
| 136 | + |
| 137 | +<<put-dfanalytics,Data frames>>, released in 7.2, allow to transform an |
| 138 | +existing index to a secondary, summarized index. 7.3 now introduces Data frame |
| 139 | +pivot transforms in order to create entity-centric indexes that can summarize |
| 140 | +the behavior of an entity. |
| 141 | + |
| 142 | +NOTE: Data frames are only available with the default distribution of {es}. |
| 143 | + |
| 144 | +// end::notable-highlights[] |
| 145 | + |
| 146 | +// tag::notable-highlights[] |
| 147 | +[float] |
| 148 | +==== Outlier detection |
| 149 | + |
| 150 | +{stack-ov}/security-privileges.html[Outlier detection] utilizes Elastic data |
| 151 | +frame indexes to evaluate source indexes across multiple dimensions and identify |
| 152 | +clusters of data based on the assigned values and which values are different |
| 153 | +from those of the clustered data point. An outlier score can be used to indicate |
| 154 | +how different an entity is from other entities in the index based on the |
| 155 | +dimensions that you supply. |
| 156 | + |
| 157 | +NOTE: Outlier detection requires a platinum license. |
| 158 | + |
| 159 | +// end::notable-highlights[] |
0 commit comments