[ 
https://issues.apache.org/jira/browse/HADOOP-14661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086779#comment-16086779
 ] 

ASF GitHub Bot commented on HADOOP-14661:
-----------------------------------------

GitHub user mandusm opened a pull request:

    https://github.com/apache/hadoop/pull/250

    HADOOP-14661. Added support for AWS S3 Requester Pays Buckets

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mandusm/hadoop mandusm/requesterPays

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hadoop/pull/250.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #250
    
----
commit e320165c181de83f375e56b841fea4dd57012501
Author: Mandus Momberg <[email protected]>
Date:   2017-07-14T01:04:18Z

    Added support for AWS S3 Requester Pays Buckets

----


> Support for AWS S3 Requester Pays Buckets using s3a filesystem 
> ---------------------------------------------------------------
>
>                 Key: HADOOP-14661
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14661
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: common, util
>    Affects Versions: 3.0.0-alpha3
>            Reporter: Mandus Momberg
>            Priority: Minor
>         Attachments: HADOOP-14661.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Amazon S3 has the ability to charge the requester for the cost of accessing 
> S3. This is called Requester Pays Buckets. 
> In order to access these buckets, each request needs to be signed with a 
> specific header. 
> http://docs.aws.amazon.com/AmazonS3/latest/dev/RequesterPaysBuckets.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to