Skip to content

Commit 48fa4aa

Browse files
elasticsearchmachinecharlotte-hoblik
elasticsearchmachine
and
charlotte-hoblik
authored
Forward port release notes for v8.17.8 (#129944)
* Forward port release notes for v8.17.8 * Update docs for v8.17.7 release * Fix typo --------- Co-authored-by: Charlotte Hoblik <[email protected]> Co-authored-by: Charlotte Hoblik <[email protected]>
1 parent 0da1f69 commit 48fa4aa

File tree

4 files changed

+190
-0
lines changed

4 files changed

+190
-0
lines changed

‎docs/reference/release-notes.asciidoc‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ This section summarizes the changes in each release.
1010
* <<release-notes-8.18.2>>
1111
* <<release-notes-8.18.1>>
1212
* <<release-notes-8.18.0>>
13+
* <<release-notes-8.17.8>>
14+
* <<release-notes-8.17.7>>
1315
* <<release-notes-8.17.6>>
1416
* <<release-notes-8.17.5>>
1517
* <<release-notes-8.17.4>>
@@ -97,6 +99,8 @@ include::release-notes/8.19.0.asciidoc[]
9799
include::release-notes/8.18.2.asciidoc[]
98100
include::release-notes/8.18.1.asciidoc[]
99101
include::release-notes/8.18.0.asciidoc[]
102+
include::release-notes/8.17.8.asciidoc[]
103+
include::release-notes/8.17.7.asciidoc[]
100104
include::release-notes/8.17.6.asciidoc[]
101105
include::release-notes/8.17.5.asciidoc[]
102106
include::release-notes/8.17.4.asciidoc[]

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

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
[[release-notes-8.17.7]]
2+
== {es} version 8.17.7
3+
4+
coming[8.17.7]
5+
6+
Also see <<breaking-changes-8.17,Breaking changes in 8.17>>.
7+
8+
[[breaking-8.17.7]]
9+
[float]
10+
=== Breaking changes
11+
12+
Snapshot/Restore::
13+
* Make S3 custom query parameter optional {es-pull}128043[#128043]
14+
15+
[[bug-8.17.7]]
16+
[float]
17+
=== Bug fixes
18+
19+
Audit::
20+
* Handle streaming request body in audit log {es-pull}127798[#127798]
21+
22+
Downsampling::
23+
* Downsampling does not consider passthrough fields as dimensions {es-pull}127752[#127752] (issue: {es-issue}125156[#125156])
24+
25+
Infra/Scripting::
26+
* Avoid nested docs in painless execute api {es-pull}127991[#127991] (issue: {es-issue}41004[#41004])
27+
28+
Relevance::
29+
* Fix: Add `NamedWriteable` for `RuleQueryRankDoc` {es-pull}128153[#128153] (issue: {es-issue}126071[#126071])
30+
31+
Security::
32+
* Remove dangling spaces wherever found {es-pull}127475[#127475]
33+
34+
TSDB::
35+
* Skip the validation when retrieving the index mode during reindexing a time series data stream {es-pull}127824[#127824]
36+
37+

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

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
[[release-notes-8.17.8]]
2+
== {es} version 8.17.8
3+
4+
Also see <<breaking-changes-8.17,Breaking changes in 8.17>>.
5+
6+
[[bug-8.17.8]]
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+
Codec::
17+
* Use new source loader when lower `docId` is accessed {es-pull}128320[#128320]
18+
19+
Data streams::
20+
* Bump APM data resource version {es-pull}129539[#129539]
21+
22+
Infra/Core::
23+
* Update AbstractXContentParser to support parsers that don't provide text characters {es-pull}129005[#129005]
24+
25+
Infra/Scripting::
26+
* Register mustache size limit setting {es-pull}119291[#119291]
27+
28+
Machine Learning::
29+
* Account for Java direct memory on machine learning nodes to prevent out-of-memory crashes. {es-pull}128742[#128742]
30+
* Ensure that anomaly detection job state update retries if master node is temoporarily unavailable {es-pull}129391[#129391] (issue: {es-issue}126148[#126148])
31+
32+
Searchable Snapshots::
33+
* Adjust unpromotable shard refresh request validation to allow `RefreshResult.NO_REFRESH` {es-pull}129176[#129176] (issue: {es-issue}129036[#129036])
34+
35+
Security::
36+
* Fix error message when changing the password for a user in the file realm {es-pull}127621[#127621]
37+
38+
[[enhancement-8.17.8]]
39+
[float]
40+
=== Enhancements
41+
42+
Authorization::
43+
* Fix unsupported privileges error message during role and API key creation {es-pull}129158[#129158] (issue: {es-issue}128132[#128132])
44+
45+

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

Lines changed: 104 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,110 @@ 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+
{es-pull}129555[#129555]
141+
38142
// end::notable-highlights[]
39143

40144

0 commit comments

Comments
 (0)