[ 
https://issues.apache.org/jira/browse/HADOOP-17198?focusedWorklogId=720348&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-720348
 ]

ASF GitHub Bot logged work on HADOOP-17198:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Feb/22 19:14
            Start Date: 03/Feb/22 19:14
    Worklog Time Spent: 10m 
      Work Description: steveloughran commented on pull request #3958:
URL: https://github.com/apache/hadoop/pull/3958#issuecomment-1029314371


   this is @bogthe's work, I've just dealt with the merge conflict caused by 
the s3guard cut.
   
   testing s3 london. assuming it and the yetus tests are happy, i will do the 
merge


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 720348)
    Time Spent: 14h 10m  (was: 14h)

> Support S3 Access Points
> ------------------------
>
>                 Key: HADOOP-17198
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17198
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.3.0
>            Reporter: Steve Loughran
>            Assignee: Bogdan Stolojan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>          Time Spent: 14h 10m
>  Remaining Estimate: 0h
>
> Improve VPC integration by supporting access points for buckets
> https://docs.aws.amazon.com/AmazonS3/latest/dev/access-points.html
> *important*: when backporting, always include HADOOP-17951 as the followup 
> patch



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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

Reply via email to