[
https://issues.apache.org/jira/browse/HADOOP-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16519436#comment-16519436
]
Sean Mackrory commented on HADOOP-15416:
----------------------------------------
+1 to the change based on the code itself - I'll do a quick sanity test before
committing too.
{quote}works OK if you list a bucket with no trailing /: hadoop s3guard diff
s3a://hwdev-steve-new{quote}
[[email protected]] other than some log formatting, I think I'm missing how
this stack trace differs from the one above - MetadataStore is initialized, but
then we fail with the same exception type in the same place. If there's more
wrong here than just not having a decent explanation with the exception we may
as well dig into it now...
> s3guard diff assert failure if source path not found
> ----------------------------------------------------
>
> Key: HADOOP-15416
> URL: https://issues.apache.org/jira/browse/HADOOP-15416
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.1.0
> Environment: s3a with fault injection turned on
> Reporter: Steve Loughran
> Assignee: Gabor Bota
> Priority: Minor
> Attachments: HADOOP-15416.001.patch
>
>
> Got an illegal argument exception trying to do a s3guard diff in a test run.
> Underlying cause: directory in supplied s3a path didn't exist
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
