[
https://issues.apache.org/jira/browse/HADOOP-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446071#comment-13446071
]
Ivan Vladimirov Ivanov commented on HADOOP-8696:
------------------------------------------------
You are right Daryn.
I am assuming that there is a need, for some reason, for the exception message
to contain details about the cause, independent of the ones that show up in the
stack trace. It will be nice if Steve would clarify if this is what he had in
mind.
> 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
