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] [Commented] (HADOOP-8696) Trash.moveToTrash should be more helpful on errors
Date Fri, 31 Aug 2012 19:53:08 GMT

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

Steve Loughran commented on HADOOP-8696:
----------------------------------------

It didn't in the output we saw from the logs -the remote client got the error string but not
the nested cause
                
> Trash.moveToTrash should be more helpful on errors
> --------------------------------------------------
>
>                 Key: HADOOP-8696
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8696
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 1.0.3
>            Reporter: Steve Loughran
>            Priority: Minor
>              Labels: newbie
>         Attachments: HADOOP-8696.patch
>
>
> When {{Trash.moveToTrash()}} catches an exception, it wraps it with an IOException: {{new
IOException("Failed to move to trash: "+path).initCause(cause);}} -but this doesn't include
the exception name in the end-user string. 
> As a result, people see the "Failed to move to trash" exception, but nobody knows what
went wrong.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message