|
1 | 1 | [[release-highlights]] |
2 | | -= Release highlights |
3 | | - |
4 | | -[partintro] |
5 | | --- |
6 | | -This section summarizes the most important changes in each release. For the |
7 | | -full list, see <<es-release-notes>> and <<breaking-changes>>. |
8 | | - |
9 | | -* <<release-highlights-7.8.0>> |
10 | | -* <<release-highlights-7.7.0>> |
11 | | -* <<release-highlights-7.6.0>> |
12 | | -* <<release-highlights-7.5.0>> |
13 | | -* <<release-highlights-7.4.0>> |
14 | | -* <<release-highlights-7.3.0>> |
15 | | -* <<release-highlights-7.2.0>> |
16 | | -* <<release-highlights-7.1.0>> |
17 | | -* <<release-highlights-7.0.0>> |
18 | | - |
19 | | --- |
20 | | - |
21 | | -include::highlights-7.8.0.asciidoc[] |
22 | | -include::highlights-7.7.0.asciidoc[] |
23 | | -include::highlights-7.6.0.asciidoc[] |
24 | | -include::highlights-7.5.0.asciidoc[] |
25 | | -include::highlights-7.4.0.asciidoc[] |
26 | | -include::highlights-7.3.0.asciidoc[] |
27 | | -include::highlights-7.2.0.asciidoc[] |
28 | | -include::highlights-7.1.0.asciidoc[] |
29 | | -include::highlights-7.0.0.asciidoc[] |
| 2 | +== What's new in {minor-version} |
| 3 | + |
| 4 | +coming[{minor-version}] |
| 5 | + |
| 6 | +Here are the highlights of what's new and improved in {es} {minor-version}! |
| 7 | +For detailed information about this release, see the |
| 8 | +<<release-notes-{elasticsearch_version}, Release notes >> and |
| 9 | +<<breaking-changes-{minor-version}, Breaking changes>>. |
| 10 | + |
| 11 | +// Add previous release to the list |
| 12 | +Other versions: |
| 13 | +{ref-bare}/7.7/release-highlights.html[7.7] |
| 14 | +| {ref-bare}/7.6/release-highlights-7.6.0.html[7.6] |
| 15 | +| {ref-bare}/7.5/release-highlights-7.5.0.html[7.5] |
| 16 | +| {ref-bare}/7.4/release-highlights-7.4.0.html[7.4] |
| 17 | +| {ref-bare}/7.3/release-highlights-7.3.0.html[7.3] |
| 18 | +| {ref-bare}/7.2/release-highlights-7.2.0.html[7.2] |
| 19 | +| {ref-bare}/7.1/release-highlights-7.1.0.html[7.1] |
| 20 | +| {ref-bare}/7.0/release-highlights-7.0.0.html[7.0] |
| 21 | + |
| 22 | + |
| 23 | +// tag::notable-highlights[] |
| 24 | +[float] |
| 25 | +=== Geo improvements |
| 26 | + |
| 27 | +We have made several improvements to geo support in {es} 7.8. |
| 28 | + |
| 29 | +- You can now run an aggregation that finds the bounding box (top left point and |
| 30 | +bottom right point) that contains all shapes matching a query. A shape is |
| 31 | +anything that is defined by multiple points. See |
| 32 | +{ref}/search-aggregations-metrics-geobounds-aggregation.html[Geo Bounds Aggregations]. |
| 33 | +- {ref}/search-aggregations-bucket-geohashgrid-aggregation.html[GeoHash grid aggregations] |
| 34 | +and {ref}/search-aggregations-bucket-geotilegrid-aggregation.html[map tile grid aggregations] |
| 35 | +allow you to group geo_points into buckets. |
| 36 | +- {ref}/search-aggregations-metrics-geocentroid-aggregation.html[Geo centroid aggregations] |
| 37 | +allow you to compute the weighted https://en.wikipedia.org/wiki/Centroid[centroid] |
| 38 | +from all coordinate values for a geo_point field. |
| 39 | + |
| 40 | +// end::notable-highlights[] |
| 41 | + |
| 42 | +// tag::notable-highlights[] |
| 43 | +[float] |
| 44 | +=== Add support for t-test aggregations |
| 45 | + |
| 46 | +{es} now supports a `t_test` metrics |
| 47 | +aggregation, which performs a statistical hypothesis test in which the test |
| 48 | +statistic follows a |
| 49 | +https://en.wikipedia.org/wiki/Student%27s_t-distribution[Student’s |
| 50 | +t-distribution] under the null hypothesis on numeric values extracted from |
| 51 | +the aggregated documents or generated by provided scripts. In practice, |
| 52 | +this will tell you if the difference between two population means are |
| 53 | +statistically significant and did not occur by chance alone. See |
| 54 | +{ref}/search-aggregations-metrics-ttest-aggregation.html[T-Test Aggregation]. |
| 55 | + |
| 56 | +// end::notable-highlights[] |
| 57 | + |
| 58 | +// tag::notable-highlights[] |
| 59 | +[float] |
| 60 | +=== Expose aggregation usage in feature usage API |
| 61 | + |
| 62 | +It is now possible to fetch a count of aggregations that have been executed |
| 63 | +via the {ref}/cluster-nodes-usage.html[node features API]. This is broken down per |
| 64 | +combination of aggregation and data type, per shard on each node, from the |
| 65 | +last restart until the time when the counts are fetched. When trying to |
| 66 | +analyze how {es} is being used in practice, it is useful to know |
| 67 | +the usage distribution across aggregations and field types. For example, |
| 68 | +you might be able to conclude that a certain part of an index is not used a |
| 69 | +lot and could perhaps can be eliminated. |
| 70 | + |
| 71 | + |
| 72 | +// end::notable-highlights[] |
| 73 | + |
| 74 | + |
| 75 | +// tag::notable-highlights[] |
| 76 | +[float] |
| 77 | +=== Support `value_count` and `avg` aggregations over histogram fields |
| 78 | + |
| 79 | +{es} now implements `value_count` and `avg` aggregations over histogram |
| 80 | +fields. |
| 81 | + |
| 82 | +When the `value_count` aggregation is computed on {ref}/histogram.html[histogram |
| 83 | +fields], the result of the aggregation is the sum of all numbers in the |
| 84 | +`counts` array of the histogram. |
| 85 | + |
| 86 | +When the average is computed on histogram fields, the result of the |
| 87 | +aggregation is the weighted average of all elements in the `values` array |
| 88 | +taking into consideration the number in the same position in the `counts` |
| 89 | +array. |
| 90 | + |
| 91 | +// end::notable-highlights[] |
| 92 | + |
| 93 | +// tag::notable-highlights[] |
| 94 | +[float] |
| 95 | +=== Reduce aggregation memory consumption |
| 96 | + |
| 97 | +{es} now attempts to save memory on the coordinating node by delaying |
| 98 | +deserialization of the shard results for an aggregation until the last |
| 99 | +second. This is helpful as it makes the shard-aggregations results "short |
| 100 | +lived" garbage. It also should shrink the memory usage of aggregations when |
| 101 | +they are waiting to be merged. |
| 102 | + |
| 103 | +Additionally, when the search is in batched reduce mode, {es} will force |
| 104 | +the results to be serialized between batch reduces in an attempt to keep |
| 105 | +the memory usage as low as possible between reductions. |
| 106 | + |
| 107 | +// end::notable-highlights[] |
| 108 | + |
| 109 | +// tag::notable-highlights[] |
| 110 | +[float] |
| 111 | +=== Scalar functions now supported in SQL aggregations |
| 112 | + |
| 113 | +When querying {es} using SQL, it is now possible to use scalar functions |
| 114 | +inside aggregations. This allows for more complex expressions, including |
| 115 | +within `GROUP BY` or `HAVING` clauses. For example: |
| 116 | + |
| 117 | +[source, sql] |
| 118 | +---- |
| 119 | +SELECT |
| 120 | + MAX(CASE WHEN a IS NULL then -1 ELSE abs(a * 10) + 1 END) AS max, |
| 121 | + b |
| 122 | +FROM test |
| 123 | +GROUP BY b |
| 124 | +HAVING |
| 125 | + MAX(CASE WHEN a IS NULL then -1 ELSE abs(a * 10) + 1 END) > 5 |
| 126 | +---- |
| 127 | + |
| 128 | +// end::notable-highlights[] |
| 129 | +// tag::notable-highlights[] |
| 130 | +[float] |
| 131 | +[[release-highlights-7.8.0-throttling]] |
| 132 | +=== Increase the performance and scalability of {transforms} with throttling |
| 133 | + |
| 134 | +{transforms-cap} achieved GA status in 7.7 and now in 7.8 they are even better |
| 135 | +with the introduction of |
| 136 | +{ref}/transform-overview.html#transform-performance[throttling]. You can spread |
| 137 | +out the impact of the {transforms} on your cluster by defining the rate at which |
| 138 | +they perform search and index requests. Set the `docs_per_second` limit when you |
| 139 | +create or update your {transform}. |
| 140 | + |
| 141 | +// end::notable-highlights[] |
| 142 | +// tag::notable-highlights[] |
| 143 | +[float] |
| 144 | +[[release-highlights-7.8.0-mml]] |
| 145 | +=== Better estimates for {ml} model memory usage |
| 146 | + |
| 147 | +For 7.8, we introduce dynamic estimation of the model memory limit for jobs in |
| 148 | +{ml-docs}/ootb-ml-jobs.html[ML solution modules]. The estimate is generated |
| 149 | +during the job creation. It uses a calculation based on the specific detectors |
| 150 | +of the job and the cardinality of the partitioning and influencer fields. It |
| 151 | +means the job setup has better default values depending on the size of the data |
| 152 | +being analyzed. |
| 153 | + |
| 154 | +// end::notable-highlights[] |
| 155 | +// tag::notable-highlights[] |
| 156 | +[float] |
| 157 | +[[release-highlights-7.8.0-loss-functions]] |
| 158 | +=== Additional loss functions for {regression} |
| 159 | + |
| 160 | +{ml-docs}/dfa-regression.html#dfa-regression-lossfunction[Loss functions] |
| 161 | +measure how well a {ml} model fits a specific data set. In 7.8, we added two new |
| 162 | +loss functions for {regression} analysis. In addition to the existing mean |
| 163 | +squared error function, there are now mean squared logarithmic error and |
| 164 | +Pseudo-Huber loss functions. These additions enable you to choose the |
| 165 | +loss function that fits best with your data set. |
| 166 | + |
| 167 | +// end::notable-highlights[] |
| 168 | + |
| 169 | +// tag::notable-highlights[] |
| 170 | +[float] |
| 171 | +[[release-highlights-7.8.0-data-visualizer]] |
| 172 | +=== Extended upload limit and explanations for Data Visualizer |
| 173 | + |
| 174 | +You can now upload files up to 1 GB in Data Visualizer. The file structure |
| 175 | +finder functionality of the Data Visualizer provides more detailed explanations |
| 176 | +after both successful and unsuccessful analysis which makes it easier to |
| 177 | +diagnose issues with file upload. |
| 178 | + |
| 179 | +// end::notable-highlights[] |
0 commit comments