hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (HADOOP-15843) s3guard bucket-info command to not print a stack trace on bucket-not-found
Date Mon, 18 Feb 2019 18:08:00 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steve Loughran reopened HADOOP-15843:
-------------------------------------

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


Mime
View raw message