[ https://issues.apache.org/jira/browse/HADOOP-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771225#comment-16771225 ]
Hudson commented on HADOOP-15843: --------------------------------- FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #15988 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/15988/]) Revert "HADOOP-15843. s3guard bucket-info command to not print a stack (stevel: rev 920a89627dd191f533ff3a3a8bca293cab59ade7) * (edit) hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/s3guard/AbstractS3GuardToolTestBase.java * (edit) hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/s3guard/S3GuardTool.java * (edit) hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/s3guard.md > 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 > Fix For: 3.3.0 > > Attachments: HADOOP-15843-001.patch, HADOOP-15843.002.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