[ 
https://issues.apache.org/jira/browse/HADOOP-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646606#comment-16646606
 ] 

Steve Loughran commented on HADOOP-15843:
-----------------------------------------

And when a DDB table is expected, but there isn't one
{code}
bin/hadoop s3guard bucket-info s3a://hwdev-steve-ireland-new/
java.io.FileNotFoundException: DynamoDB table 'hwdev-steve-ireland-new' does 
not exist in region eu-west-1; auto-creation is turned off
2018-10-11 16:20:33,946 [main] INFO  util.ExitUtil 
(ExitUtil.java:terminate(210)) - Exiting with status 44: 
java.io.FileNotFoundException: DynamoDB table 'hwdev-steve-ireland-new' does 
not exist in region eu-west-1; auto-creation is turned off
{code}

I think this is the correct behaviour. The error message is already covered in 
the troubleshooting docs

> s3guard bucket-info command to not print a stack trace on bucket-not-found
> --------------------------------------------------------------------------
>
>                 Key: HADOOP-15843
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15843
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.3.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> when you go {{hadoop s3guard bucket-info s3a://bucket-which-doesnt-exist}} 
> you get a full stack trace on the failure. This is overkill: all the caller 
> needs to know is the bucket isn't there.
> Proposed: catch FNFE and treat as special, have return code of "44", "not 
> found".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to