You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Adam Antal (JIRA)" <ji...@apache.org> on 2019/01/11 16:08:00 UTC
[jira] [Commented] (HADOOP-15843) s3guard bucket-info command to
not print a stack trace on bucket-not-found
[ https://issues.apache.org/jira/browse/HADOOP-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16740520#comment-16740520 ]
Adam Antal commented on HADOOP-15843:
-------------------------------------
I looked through the patch, and tested it on eu-ireland ({{eu-west-1}}). The tests are failing, and I'm on fixing them and add new ones.
Also during the test I got an NPE as well, but it is discussed separately here: HADOOP-16043.
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org