[ https://issues.apache.org/jira/browse/HADOOP-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742125#comment-16742125 ]
Gabor Bota commented on HADOOP-15843: ------------------------------------- The modification in {{initMetadataStore}} is not needed, since I've fixed it in HADOOP-15845, so {{hasFileSystem}} check is not needed. > 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 > Assignee: Adam Antal > Priority: Minor > Attachments: HADOOP-15843-001.patch > > > 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-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org