Skip to content

Commit e561298

Browse files
Add release notes for v8.19.2 release (#132696)
* Update docs for v8.19.2 release
1 parent ab93718 commit e561298

File tree

2 files changed

+59
-0
lines changed

2 files changed

+59
-0
lines changed

docs/reference/release-notes.asciidoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@
66

77
This section summarizes the changes in each release.
88

9+
* <<release-notes-8.19.2>>
910
* <<release-notes-8.19.1>>
1011
* <<release-notes-8.19.0>>
1112
* <<release-notes-8.18.4>>
@@ -99,6 +100,7 @@ This section summarizes the changes in each release.
99100

100101
--
101102

103+
include::release-notes/8.19.2.asciidoc[]
102104
include::release-notes/8.19.1.asciidoc[]
103105
include::release-notes/8.19.0.asciidoc[]
104106
include::release-notes/8.18.4.asciidoc[]
Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
[[release-notes-8.19.2]]
2+
== {es} version 8.19.2
3+
4+
coming[8.19.2]
5+
6+
Also see <<breaking-changes-8.19,Breaking changes in 8.19>>.
7+
8+
[[bug-8.19.2]]
9+
[float]
10+
=== Bug fixes
11+
12+
Aggregations::
13+
+
14+
.Validate parent aggregation type in `bucket_script`
15+
[%collapsible]
16+
===============
17+
The `bucket_script` pipeline aggregation didn’t validate that its parent aggregation was a multi-bucket aggregation.
18+
This caused a `ClassCastException` at runtime when the parent was not multi-bucket.
19+
{es-pull}132320[#132320] adds a validation step so the aggregation fails early, preventing the runtime error. (issue: {es-issue}132272[#132272])
20+
===============
21+
22+
Codec::
23+
+
24+
.Use local segment `fieldInfos` for TSDB merge stats
25+
[%collapsible]
26+
===============
27+
Merging shrink TSDB or LogsDB indices in versions 8.19 or 9.1+ could fail when using addIndexes to combine Lucene segments directly.
28+
In these cases, fieldInfos could differ between shards and the merged segment, causing incorrect merge statistics.
29+
PR {es-pull}132597[#132597] updates the process to use `fieldInfos` from each segment instead of the merged segment, ensuring accurate stats and preventing merge failures.
30+
===============
31+
+
32+
.Remove unused `tsdb_doc_values_optimized_merge` feature flag in 8.19
33+
[%collapsible]
34+
===============
35+
In 8.19, the `tsdb_doc_values_optimized_merge` optimization was unintentionally disabled because its feature flag was not removed as planned.
36+
This happened when the original change failed to merge due to CI issues.
37+
{es-pull}128459[#128459] removes the leftover flag, enabling the optimization as intended.
38+
===============
39+
40+
Mapping::
41+
+
42+
.Calculate text string length correctly for code points outside BMP
43+
[%collapsible]
44+
===============
45+
Strings parsed with the optimized UTF-8 parsing path had incorrect length calculations for characters outside the basic multilingual plane (BMP).
46+
These characters require two UTF-16 code units, but the optimized path did not account for this, causing mismatches with the non-optimized path.
47+
{es-pull}132593[#132593] fixes the calculation to ensure consistent and correct string lengths.
48+
===============
49+
50+
[[enhancement-8.19.2]]
51+
[float]
52+
=== Enhancements
53+
54+
Authorization::
55+
* Adds `manage`, `create_index`, `read`, `index`, `write`, and `delete` privileges for the `kibana_system` role on third-party agent indices used by ExtraHop (logs-extrahop.investigation-*) and Qualys GAV (logs-qualys_gav.asset-*). This ensures ILM policies can delete these indices without permission errors. {es-pull}132387[#132387] (issue: {es-issue}131825[#131825])
56+
57+

0 commit comments

Comments
 (0)