Steve Loughran created HADOOP-15503:
---------------------------------------
Summary: 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
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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
