Skip to content

Commit 2512826

Browse files
committed
Revert "Update docs/changelog/128043.yaml"
This reverts commit 6cca2b3.
1 parent 6cca2b3 commit 2512826

File tree

1 file changed

+11
-8
lines changed

1 file changed

+11
-8
lines changed

docs/changelog/128043.yaml

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,19 @@
11
pr: 128043
22
summary: Make S3 custom query parameter optional
33
area: Snapshot/Restore
4-
type: "breaking, enhancement"
4+
type: breaking
55
issues: []
66
breaking:
77
title: Make S3 custom query parameter optional
88
area: Cluster and node setting
9-
details: "Earlier versions of Elasticsearch would record the purpose of each S3\
10-
\ API call using the `?x-purpose=` custom query parameter. This isn't believed\
11-
\ to be necessary outside of the ECH/ECE/ECK/... managed services, and it adds\
12-
\ rather a lot to the request logs, so with this change we make the feature optional\
13-
\ and disabled by default."
14-
impact: "If you wish to reinstate the old behaviour on a S3 repository, set `s3.client.${CLIENT_NAME}.add_purpose_custom_query_parameter`\
15-
\ to `true` for the relevant client."
9+
details: >-
10+
Earlier versions of Elasticsearch would record the purpose of each S3 API
11+
call using the `?x-purpose=` custom query parameter. This isn't believed to
12+
be necessary outside of the ECH/ECE/ECK/... managed services, and it adds
13+
rather a lot to the request logs, so with this change we make the feature
14+
optional and disabled by default.
15+
impact: >-
16+
If you wish to reinstate the old behaviour on a S3 repository, set
17+
`s3.client.${CLIENT_NAME}.add_purpose_custom_query_parameter` to `true`
18+
for the relevant client.
1619
notable: false

0 commit comments

Comments
 (0)