hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Antal (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HADOOP-15843) s3guard bucket-info command to not print a stack trace on bucket-not-found
Date Fri, 23 Nov 2018 13:30:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16697121#comment-16697121
] 

Adam Antal edited comment on HADOOP-15843 at 11/23/18 1:29 PM:
---------------------------------------------------------------

Hi [~stevel@apache.org], did you have a patch to this issue, or can I contribute?


was (Author: adam.antal):
Hi [~stevel@apache.org], did you a patch to this issue, or can I contribute?

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


Mime
View raw message