HADOOP-19860. S3A: support custom per-request-type S3 and STS headers#8417
Open
EnricoMi wants to merge 1 commit intoapache:trunkfrom
Open
HADOOP-19860. S3A: support custom per-request-type S3 and STS headers#8417EnricoMi wants to merge 1 commit intoapache:trunkfrom
EnricoMi wants to merge 1 commit intoapache:trunkfrom
Conversation
29e6332 to
6934987
Compare
|
💔 -1 overall
This message was automatically generated. |
6934987 to
b5b309f
Compare
|
💔 -1 overall
This message was automatically generated. |
Contributor
|
Is this a real need? it's adding more complexity to the system |
Contributor
Author
|
It is a generalization of #7379 and required for custom headers that are not allowed by all requests. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
Similar to #7379 (HADOOP-18562), users might want to send custom headers for specific requests only.
With
Only
DeleteObjectRequestrequests have a custom headerx-amz-delete-contents: true.Note:
DeleteObjectRequestis only an example here. Any request class name could be used here.See:
How was this patch tested?
There is a unit test verifying the headers are injected into the AWS request objects.
Integration test
ITestS3AContractDeletehas been run against a company S3 point and headers show up only in the expected (delete) requests.For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?AI Tooling
No AI tooling has been used.