Skip to content

Commit 850467e

Browse files
author
elasticsearchmachine
committed
Forward port release notes for v8.18.2
1 parent b0beb54 commit 850467e

File tree

4 files changed

+179
-6
lines changed

4 files changed

+179
-6
lines changed

‎docs/reference/migration/migrate_8_18.asciidoc‎

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,20 @@ Before this change, in case of shard failures, EQL queries always returned an er
8181
EQL queries that would previously fail due to shard failures, will now succeed and return partial results. The previous defaults can be restored by setting `xpack.eql.default_allow_partial_results` cluster setting to `false` or setting with `allow_partial_search_results` to `false` in the query request.
8282
====
8383

84+
[discrete]
85+
[[breaking_818_esql_changes]]
86+
==== ES|QL changes
87+
88+
[[limit_scope_skip_unavailable_setting_remote_clusters]]
89+
.Limit the scope of the skip_unavailable setting for remote clusters
90+
[%collapsible]
91+
====
92+
*Details* +
93+
Before this change, ES|QL would honor the skip_unavailable setting for nonmatching indices errors at planning time, meaning that when a query with a concrete (non-wildcarded) index was issued to a cluster where skip_unavailable=true, the index would be skipped, allowing the query to proceed on any other specified clusters rather than returning an error.
94+
95+
*Impact* +
96+
Remote clusters, regardless of their skip_unavailable setting, will now use the same logic as the local cluster for index expression analysis at plan time. As a result, any missing concrete index in your index expression will return an error rather than partial results.
97+
====
8498

8599
[discrete]
86100
[[deprecated-8.18]]

‎docs/reference/release-notes.asciidoc‎

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

99
* <<release-notes-8.19.0>>
10+
* <<release-notes-8.18.2>>
1011
* <<release-notes-8.18.1>>
1112
* <<release-notes-8.18.0>>
1213
* <<release-notes-8.17.6>>
@@ -93,6 +94,7 @@ This section summarizes the changes in each release.
9394
--
9495

9596
include::release-notes/8.19.0.asciidoc[]
97+
include::release-notes/8.18.2.asciidoc[]
9698
include::release-notes/8.18.1.asciidoc[]
9799
include::release-notes/8.18.0.asciidoc[]
98100
include::release-notes/8.17.6.asciidoc[]

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

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
[[release-notes-8.18.2]]
2+
== {es} version 8.18.2
3+
4+
Also see <<breaking-changes-8.18,Breaking changes in 8.18>>.
5+
6+
[[breaking-8.18.2]]
7+
[float]
8+
=== Breaking changes
9+
10+
Snapshot/Restore::
11+
* Make S3 custom query parameter optional {es-pull}128043[#128043]
12+
13+
[[bug-8.18.2]]
14+
[float]
15+
=== Bug fixes
16+
17+
Aggregations::
18+
* Fix a bug in `significant_terms` {es-pull}127975[#127975]
19+
20+
Audit::
21+
* Handle streaming request body in audit log {es-pull}127798[#127798]
22+
23+
Data streams::
24+
* Fix system data streams incorrectly showing up in the list of template validation problems {es-pull}128161[#128161]
25+
26+
Downsampling::
27+
* Downsampling does not consider passthrough fields as dimensions {es-pull}127752[#127752] (issue: {es-issue}125156[#125156])
28+
29+
ES|QL::
30+
* Ensure ordinal builder emit ordinal blocks {es-pull}127949[#127949]
31+
* Fix union types in CCS {es-pull}128111[#128111]
32+
33+
Infra/Core::
34+
* Add missing `outbound_network` entitlement to x-pack-core {es-pull}126992[#126992] (issue: {es-issue}127003[#127003])
35+
* Check hidden frames in entitlements {es-pull}127877[#127877]
36+
37+
Infra/Scripting::
38+
* Avoid nested docs in painless execute api {es-pull}127991[#127991] (issue: {es-issue}41004[#41004])
39+
40+
Logs::
41+
* Fix an authorization error when LogsPatternUsageService attempts to update `logsdb.prior_logs_usage` cluster setting. {es-pull}128050[#128050]
42+
43+
Machine Learning::
44+
* Append all data to Chat Completion buffer {es-pull}127658[#127658]
45+
* Fix services API Google Vertex AI Rerank location field requirement {es-pull}127856[#127856]
46+
* Use internal user for internal inference action {es-pull}128327[#128327]
47+
48+
Relevance::
49+
* Fix: Add `NamedWriteable` for `RuleQueryRankDoc` {es-pull}128153[#128153] (issue: {es-issue}126071[#126071])
50+
51+
Security::
52+
* Remove dangling spaces wherever found {es-pull}127475[#127475]
53+
54+
Snapshot/Restore::
55+
* Add missing entitlement to `repository-azure` {es-pull}128047[#128047] (issue: {es-issue}128046[#128046])
56+
57+
TSDB::
58+
* Skip the validation when retrieving the index mode during reindexing a time series data stream {es-pull}127824[#127824]
59+
60+
[[enhancement-8.18.2]]
61+
[float]
62+
=== Enhancements
63+
64+
Authentication::
65+
* Http proxy support in JWT realm {es-pull}127337[#127337] (issue: {es-issue}114956[#114956])
66+
67+

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

Lines changed: 96 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -33,12 +33,102 @@ Other versions:
3333

3434
endif::[]
3535

36-
// The notable-highlights tag marks entries that
37-
// should be featured in the Stack Installation and Upgrade Guide:
3836
// tag::notable-highlights[]
39-
// [discrete]
40-
// === Heading
41-
//
42-
// Description.
37+
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+
43132
// end::notable-highlights[]
44133

134+

0 commit comments

Comments
 (0)