hadoop-common-issues mailing list archives

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

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

Gabor Bota commented on HADOOP-15843:
-------------------------------------

Thanks [~stevel@apache.org], I've ran some tests as a regression an got some errors on dynamo.
I think we should address those first. I'll create the issues for those.

> 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


Mime
View raw message