@@ -11,7 +11,8 @@ For detailed information about this release, see the <<es-release-notes>> and
11
11
// Add previous release to the list
12
12
Other versions:
13
13
14
- {ref-bare}/8.14/release-highlights.html[8.14]
14
+ {ref-bare}/8.15/release-highlights.html[8.15]
15
+ | {ref-bare}/8.14/release-highlights.html[8.14]
15
16
| {ref-bare}/8.13/release-highlights.html[8.13]
16
17
| {ref-bare}/8.12/release-highlights.html[8.12]
17
18
| {ref-bare}/8.11/release-highlights.html[8.11]
@@ -29,60 +30,13 @@ Other versions:
29
30
30
31
endif::[]
31
32
33
+ // The notable-highlights tag marks entries that
34
+ // should be featured in the Stack Installation and Upgrade Guide:
32
35
// tag::notable-highlights[]
33
-
34
- [discrete]
35
- [[stored_fields_are_compressed_with_zstandard_instead_of_lz4_deflate]]
36
- === Stored fields are now compressed with ZStandard instead of LZ4/DEFLATE
37
- Stored fields are now compressed by splitting documents into blocks, which
38
- are then compressed independently with ZStandard. `index.codec: default`
39
- (default) uses blocks of at most 14kB or 128 documents compressed with level
40
- 0, while `index.codec: best_compression` uses blocks of at most 240kB or
41
- 2048 documents compressed at level 3. On most datasets that we tested
42
- against, this yielded storage improvements in the order of 10%, slightly
43
- faster indexing and similar retrieval latencies.
44
-
45
- {es-pull}103374[#103374]
46
-
36
+ // [discrete]
37
+ // === Heading
38
+ //
39
+ // Description.
47
40
// end::notable-highlights[]
48
41
49
42
50
- [discrete]
51
- [[new_custom_parser_for_iso_8601_datetimes]]
52
- === New custom parser for ISO-8601 datetimes
53
- This introduces a new custom parser for ISO-8601 datetimes, for the `iso8601`, `strict_date_optional_time`, and
54
- `strict_date_optional_time_nanos` built-in date formats. This provides a performance improvement over the
55
- default Java date-time parsing. Whilst it maintains much of the same behaviour,
56
- the new parser does not accept nonsensical date-time strings that have multiple fractional seconds fields
57
- or multiple timezone specifiers. If the new parser fails to parse a string, it will then use the previous parser
58
- to parse it. If a large proportion of the input data consists of these invalid strings, this may cause
59
- a small performance degradation. If you wish to force the use of the old parsers regardless,
60
- set the JVM property `es.datetime.java_time_parsers=true` on all ES nodes.
61
-
62
- {es-pull}106486[#106486]
63
-
64
- [discrete]
65
- [[preview_support_for_connection_type_domain_isp_databases_in_geoip_processor]]
66
- === Preview: Support for the 'Connection Type, 'Domain', and 'ISP' databases in the geoip processor
67
- As a Technical Preview, the {ref}/geoip-processor.html[`geoip`] processor can now use the commercial
68
- https://dev.maxmind.com/geoip/docs/databases/connection-type[GeoIP2 'Connection Type'],
69
- https://dev.maxmind.com/geoip/docs/databases/domain[GeoIP2 'Domain'],
70
- and
71
- https://dev.maxmind.com/geoip/docs/databases/isp[GeoIP2 'ISP']
72
- databases from MaxMind.
73
-
74
- {es-pull}108683[#108683]
75
-
76
- [discrete]
77
- [[update_elasticsearch_to_lucene_9_11]]
78
- === Update Elasticsearch to Lucene 9.11
79
- Elasticsearch is now updated using the latest Lucene version 9.11.
80
- Here are the full release notes:
81
- But, here are some particular highlights:
82
- - Usage of MADVISE for better memory management: https://github.com/apache/lucene/pull/13196
83
- - Use RWLock to access LRUQueryCache to reduce contention: https://github.com/apache/lucene/pull/13306
84
- - Speedup multi-segment HNSW graph search for nested kNN queries: https://github.com/apache/lucene/pull/13121
85
- - Add a MemorySegment Vector scorer - for scoring without copying on-heap vectors: https://github.com/apache/lucene/pull/13339
86
-
87
- {es-pull}109219[#109219]
88
-
0 commit comments