You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2018/10/11 14:22:00 UTC

[jira] [Created] (HADOOP-15843) s3guard bucket-info command to not print a stack trace on bucket-not-found

Steve Loughran created HADOOP-15843:
---------------------------------------

             Summary: 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


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: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org