Skip to content

Commit d269c75

Browse files
author
elasticsearchmachine
committed
Forward port release notes for v8.18.3
1 parent 2e6d415 commit d269c75

File tree

3 files changed

+190
-0
lines changed

3 files changed

+190
-0
lines changed

‎docs/reference/release-notes.asciidoc‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,12 @@
77
This section summarizes the changes in each release.
88

99
* <<release-notes-8.19.0>>
10+
* <<release-notes-8.18.3>>
1011
* <<release-notes-8.18.2>>
1112
* <<release-notes-8.18.1>>
1213
* <<release-notes-8.18.0>>
14+
* <<release-notes-8.17.8>>
15+
* <<release-notes-8.17.7>>
1316
* <<release-notes-8.17.6>>
1417
* <<release-notes-8.17.5>>
1518
* <<release-notes-8.17.4>>
@@ -94,9 +97,12 @@ This section summarizes the changes in each release.
9497
--
9598

9699
include::release-notes/8.19.0.asciidoc[]
100+
include::release-notes/8.18.3.asciidoc[]
97101
include::release-notes/8.18.2.asciidoc[]
98102
include::release-notes/8.18.1.asciidoc[]
99103
include::release-notes/8.18.0.asciidoc[]
104+
include::release-notes/8.17.8.asciidoc[]
105+
include::release-notes/8.17.7.asciidoc[]
100106
include::release-notes/8.17.6.asciidoc[]
101107
include::release-notes/8.17.5.asciidoc[]
102108
include::release-notes/8.17.4.asciidoc[]

‎docs/reference/release-notes/8.18.3.asciidoc‎

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
[[release-notes-8.18.3]]
2+
== {es} version 8.18.3
3+
4+
Also see <<breaking-changes-8.18,Breaking changes in 8.18>>.
5+
6+
[[bug-8.18.3]]
7+
[float]
8+
=== Bug fixes
9+
10+
Aggregations::
11+
* Aggs: Fix significant terms not finding background docuemnts for nested fields {es-pull}128472[#128472] (issue: {es-issue}101163[#101163])
12+
13+
Authorization::
14+
* Prevent invalid privileges in manage roles privilege {es-pull}128532[#128532] (issue: {es-issue}127496[#127496])
15+
16+
CCS::
17+
* Handle the indices pattern `["*", "-*"]` when grouping indices by cluster name {es-pull}128610[#128610]
18+
19+
Codec::
20+
* Use new source loader when lower `docId` is accessed {es-pull}128320[#128320]
21+
22+
Data streams::
23+
* Bump APM data resource version {es-pull}129547[#129547]
24+
25+
ES|QL::
26+
* Fix `FieldAttribute` name usage in `InferNonNullAggConstraint` {es-pull}128910[#128910]
27+
* Support DATE_NANOS in LOOKUP JOIN {es-pull}127962[#127962] (issue: {es-issue}127249[#127249])
28+
* Throw ISE instead of IAE for illegal block in page {es-pull}128960[#128960]
29+
30+
Geo::
31+
* Added geometry validation for GEO types to exit early on invalid latitudes {es-pull}128259[#128259] (issue: {es-issue}128234[#128234])
32+
33+
IdentityProvider::
34+
* Improve cache invalidation in IdP SP cache {es-pull}128890[#128890]
35+
36+
Infra/Core::
37+
* Update AbstractXContentParser to support parsers that don't provide text characters {es-pull}129005[#129005]
38+
39+
Infra/Plugins::
40+
* Add complete attribute to .fleet-agents docs {es-pull}127651[#127651]
41+
42+
Machine Learning::
43+
* Account for Java direct memory on machine learning nodes to prevent out-of-memory crashes. {es-pull}128742[#128742]
44+
* Ensure that anomaly detection job state update retries if master node is temoporarily unavailable {es-pull}129391[#129391] (issue: {es-issue}126148[#126148])
45+
* Fix NPE when `date_buckets` aggregation is missing in the response {es-pull}128974[#128974]
46+
* Pass timeout to chat completion {es-pull}128338[#128338]
47+
* Prevent ML data retention logic from failing when deleting documents in read-only indices {es-pull}125408[#125408]
48+
49+
Search::
50+
* Fix minmax normalizer handling of single-doc result sets {es-pull}128689[#128689]
51+
* Fix missing highlighting in `match_all` queries for `semantic_text` fields {es-pull}128702[#128702]
52+
53+
Searchable Snapshots::
54+
* Adjust unpromotable shard refresh request validation to allow `RefreshResult.NO_REFRESH` {es-pull}129176[#129176] (issue: {es-issue}129036[#129036])
55+
56+
Security::
57+
* Fix error message when changing the password for a user in the file realm {es-pull}127621[#127621]
58+
59+
Vector Search::
60+
* Fix NPE in `flat_bbq` scorer when all vectors are missing {es-pull}129548[#129548]
61+
62+
[[enhancement-8.18.3]]
63+
[float]
64+
=== Enhancements
65+
66+
Authorization::
67+
* Fix unsupported privileges error message during role and API key creation {es-pull}129158[#129158] (issue: {es-issue}128132[#128132])
68+
69+
ES|QL::
70+
* Support partial sort fields in TopN pushdown {es-pull}116043[#116043] (issue: {es-issue}114515[#114515])
71+
72+
[[upgrade-8.18.3]]
73+
[float]
74+
=== Upgrades
75+
76+
Packaging::
77+
* Update default docker base image to Ubuntu 24.04 {es-pull}128732[#128732]
78+
79+

‎docs/reference/release-notes/highlights.asciidoc‎

Lines changed: 105 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,111 @@ endif::[]
3535

3636
// tag::notable-highlights[]
3737

38+
[discrete]
39+
[[upgrade_repository_s3_to_aws_sdk_v2]]
40+
=== Upgrade `repository-s3` to AWS SDK v2
41+
In earlier versions of {es} the `repository-s3` plugin was based on the AWS SDK v1. AWS will withdraw support for this SDK before the end of the life of {es} {minor-version} so we have migrated this plugin to the newer AWS SDK v2.
42+
The two SDKs are not quite compatible, so please check the breaking changes documentation and test the new version thoroughly before upgrading any production workloads.
43+
44+
{es-pull}126843[#126843]
45+
46+
[discrete]
47+
[[add_ability_to_redirect_ingestion_failures_on_data_streams_to_failure_store]]
48+
=== Add ability to redirect ingestion failures on data streams to a failure store
49+
Documents that encountered ingest pipeline failures or mapping conflicts
50+
would previously be returned to the client as errors in the bulk and
51+
index operations. Many client applications are not equipped to respond
52+
to these failures. This leads to the failed documents often being
53+
dropped by the client which cannot hold the broken documents
54+
indefinitely. In many end user workloads, these failed documents
55+
represent events that could be critical signals for observability or
56+
security use cases.
57+
58+
To help mitigate this problem, data streams can now maintain a "failure
59+
store" which is used to accept and hold documents that fail to be
60+
ingested due to preventable configuration errors. The data stream's
61+
failure store operates like a separate set of backing indices with their
62+
own mappings and access patterns that allow Elasticsearch to accept
63+
documents that would otherwise be rejected due to unhandled ingest
64+
pipeline exceptions or mapping conflicts.
65+
66+
Users can enable redirection of ingest failures to the failure store on
67+
new data streams by specifying it in the new `data_stream_options` field
68+
inside of a component or index template:
69+
70+
[source,yaml]
71+
----
72+
PUT _index_template/my-template
73+
{
74+
"index_patterns": ["logs-test-*"],
75+
"data_stream": {},
76+
"template": {
77+
"data_stream_options": {
78+
"failure_store": {
79+
"enabled": true
80+
}
81+
}
82+
}
83+
}'
84+
----
85+
86+
Existing data streams can be configured with the new data stream
87+
`_options` endpoint:
88+
89+
[source,yaml]
90+
----
91+
PUT _data_stream/logs-test-apache/_options
92+
{
93+
"failure_store": {
94+
"enabled": "true"
95+
}
96+
}
97+
----
98+
99+
When redirection is enabled, any ingestion related failures will be
100+
captured in the failure store if the cluster is able to, along with the
101+
timestamp that the failure occurred, details about the error
102+
encountered, and the document that could not be ingested. Since failure
103+
stores are a kind of Elasticsearch index, we can search the data stream
104+
for the failures that it has collected. The failures are not shown by
105+
default as they are stored in different indices than the normal data
106+
stream data. In order to retrieve the failures, we use the `_search` API
107+
along with a new bit of index pattern syntax, the `::` selector.
108+
109+
[source,yaml]
110+
----
111+
POST logs-test-apache::failures/_search
112+
----
113+
114+
This index syntax informs the search operation to target the indices in
115+
its failure store instead of its backing indices. It can be mixed in a
116+
number of ways with other index patterns to include their failure store
117+
indices in the search operation:
118+
119+
[source,yaml]
120+
----
121+
POST logs-*::failures/_search
122+
POST logs-*,logs-*::failures/_search
123+
POST *::failures/_search
124+
POST _query
125+
{
126+
"query": "FROM my_data_stream*::failures"
127+
}
128+
----
129+
130+
{es-pull}126973[#126973]
131+
132+
[discrete]
133+
[[upgrade_to_lucene_9_12_2]]
134+
=== Upgrade to lucene 9.12.2
135+
* Reduce NeighborArray on-heap memory during HNSW graph building
136+
* Fix IndexSortSortedNumericDocValuesRangeQuery for integer sorting
137+
* ValueSource.fromDoubleValuesSource(dvs).getSortField() would throw errors when used if the DoubleValuesSource needed scores
138+
* Disable connectedComponents logic in HNSW graph building.
139+
----
140+
141+
{es-pull}129555[#129555]
142+
38143
// end::notable-highlights[]
39144
40145

0 commit comments

Comments
 (0)