[
https://issues.apache.org/jira/browse/HADOOP-18562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17948693#comment-17948693
]
ASF GitHub Bot commented on HADOOP-18562:
-----------------------------------------
adideshpande commented on PR #7379:
URL: https://github.com/apache/hadoop/pull/7379#issuecomment-2845236949
@ahmarsuhail Sure, I have rebased it on top of origin/trunk and it looks
cleaner now with only 4 file changes (and 9 commits). Could you please take a
look? Let me know if you need this to be rebased into a single commit. Thanks.
P.S: My local repo had become messy while I was trying to fetch and merge a
few commits, and fix some conflicts. I had to nuke it and checkout the repo
locally again :)
> S3A: support custom S3 and STS headers
> --------------------------------------
>
> Key: HADOOP-18562
> URL: https://issues.apache.org/jira/browse/HADOOP-18562
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Daniel Carl Jones
> Assignee: Prerak Pradhan
> Priority: Minor
> Labels: pull-request-available
>
> Some users have the use case where for a particular S3A filesystem, they
> would like to set one or more headers to a static value.
> We might imagine a set of configurations properties with a common prefix,
> where the suffix determines the header name and the value of the property
> determines the value of the header.
> Per-filesystem headers can be set using the per-bucket configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
