File tree Expand file tree Collapse file tree 1 file changed +11
-8
lines changed Expand file tree Collapse file tree 1 file changed +11
-8
lines changed Original file line number Diff line number Diff line change 11pr : 128043
22summary : Make S3 custom query parameter optional
33area : Snapshot/Restore
4- type : " breaking, enhancement "
4+ type : breaking
55issues : []
66breaking :
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
You can’t perform that action at this time.
0 commit comments