[
https://issues.apache.org/jira/browse/HDFS-9799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe Zhang updated HDFS-9799:
----------------------------
Attachment: HDFS-9799.00.patch
The source of the {{IOException}} is from {{getEZForPath}}. So when
{{getEZForPath}} gets an exception -- meaning that the EZ of the given path
cannot be determined at the time of calling, we should just return the Trash
dir of the user's home. Even if the path does belong to an EZ, this will just
mean the {{rm}} will fail later. With the added WARN message, the calling
application should be able to obtain the RC of the {{rm}} failure.
[~andrew.wang] [~atm] Could you take a look? Thanks.
> Reimplement getCurrentTrashDir to remove incompatibility
> --------------------------------------------------------
>
> Key: HDFS-9799
> URL: https://issues.apache.org/jira/browse/HDFS-9799
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.8.0
> Reporter: Zhe Zhang
> Assignee: Zhe Zhang
> Priority: Blocker
> Attachments: HDFS-9799.00.patch
>
>
> HDFS-8831 changed the signature of {{TrashPolicy#getCurrentTrashDir}} by
> adding an IOException. This breaks other applications using this public API.
> This JIRA aims to reimplement the logic to safely handle the IOException
> within HDFS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
