[
https://issues.apache.org/jira/browse/HADOOP-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646501#comment-16646501
]
Steve Loughran commented on HADOOP-15843:
-----------------------------------------
Note this does the same for all other commands which attempt to instantiate the
s3a URL
{code}
bin/hadoop s3guard set-capacity s3a://dfdfdfggg
java.io.FileNotFoundException: Bucket dfdfdfggg does not exist
2018-10-11 15:32:00,893 [main] INFO util.ExitUtil
(ExitUtil.java:terminate(210)) - Exiting with status 44:
java.io.FileNotFoundException: Bucket dfdfdfggg does not exist
{code}
this is good: it's exactly the same issue
> 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]
