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

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

                Author: ASF GitHub Bot
            Created on: 16/May/22 11:44
            Start Date: 16/May/22 11:44
    Worklog Time Spent: 10m 
      Work Description: steveloughran commented on code in PR #4309:
URL: https://github.com/apache/hadoop/pull/4309#discussion_r873626149


##########
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md:
##########
@@ -1609,7 +1609,7 @@ You can also use an Access Point name as a path URI such 
as `s3a://finance-team-
 configuring the `.accesspoint.arn` property as a per-bucket override:

Review Comment:
   i think this whole paragraph and example can be cut; as the only way to set 
an AP binding is on a per-bucket basis.





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

    Worklog Id:     (was: 770785)
    Time Spent: 50m  (was: 40m)

> s3a access point xml examples are wrong
> ---------------------------------------
>
>                 Key: HADOOP-18234
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18234
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation, fs/s3
>    Affects Versions: 3.3.2
>            Reporter: Steve Loughran
>            Assignee: Ashutosh Gupta
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> the examples of s3a access point bindings are wrong, as the .bucket prefix is 
> missing
> {code}
> <property>
>     <name>fs.s3a.sample-bucket.accesspoint.arn</name>
>     <value> {ACCESSPOINT_ARN_HERE} </value>
>     <description>Configure S3a traffic to use this AccessPoint</description>
> </property>
> {code}
> the property should be fs.s3a.bucket.sample-bucket.accesspoint.arn



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

Reply via email to