hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-7114) FsShell should dump all exceptions at DEBUG level
Date Sat, 05 Mar 2011 00:43:46 GMT

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

Hudson commented on HADOOP-7114:

Integrated in Hadoop-Common-trunk-Commit #517 (See [https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/517/])

> FsShell should dump all exceptions at DEBUG level
> -------------------------------------------------
>                 Key: HADOOP-7114
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7114
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>             Fix For: 0.23.0
>         Attachments: hadoop-7114.txt
> Most of the FsShell commands catch exceptions and then just print out an error like "foo:
" + e.getLocalizedMessage(). This is fine when the exception is "user-facing" (eg permissions
errors) but in the case of a user hitting a bug you get a useless error message with no stack
trace. For example, something "chmod: null" in the case of a NullPointerException bug.
> It would help debug these cases for users and developers if we also logged the exception
with full trace at DEBUG level.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message