[
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.01.patch
Thanks Andrew for the review.
The IOException logic in {{getTrashRoots}} is a little more complicated. Even
the unencrypted case throws an exception caused by {{exists}} etc. If we
swallow those exceptions we need to think about a meaningful return value
(e.g., an empty collection?). Returning an empty collection also means we won't
have detailed exception about which path caused issues.
> 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-9799.01.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)
