[
https://issues.apache.org/jira/browse/HADOOP-15503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-15503:
------------------------------------
Parent: HADOOP-18067 (was: HADOOP-17566)
> strip s3.amazonaws.com off hostnames before making s3a calls
> ------------------------------------------------------------
>
> Key: HADOOP-15503
> URL: https://issues.apache.org/jira/browse/HADOOP-15503
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.1.0
> Reporter: Steve Loughran
> Priority: Minor
>
> If you copy an http URL https://bucketname.s3.amazonaws.com/ and convert to
> an s3a one by replacing the schema, you can try to list
> {code}
> bin/hadoop fs -ls -r s3a://hwdev-steve-new.s3.amazonaws.com/
> {code}
> But do that and you get told there's no such bucket
> {code}
> ls: Bucket hwdev-steve-new.s3.amazonaws.com does not exist
> {code}
> This is non-intuitive, and catches me out.
> We could strip this automatically during initialization to produce the actual
> bucket, which would need to be done before any per-bucket init is done.
> I do worry about what could break though
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
