[
https://issues.apache.org/jira/browse/HDFS-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003923#comment-15003923
]
Rakesh R commented on HDFS-9348:
--------------------------------
In this jira I've included both erasurecoding and encrptionzone changes. I'm
attaching separate branch-2 patch to fix the encryption zone. Do we need to fix
encryption zone in a separate jira to avoid confusion because if some one sees
the jira title(says erasure coding which is available only in trunk now) and
fix version branch-2 ?
> DFS GetErasureCodingPolicy API on a non-existent file should be handled
> properly
> --------------------------------------------------------------------------------
>
> Key: HDFS-9348
> URL: https://issues.apache.org/jira/browse/HDFS-9348
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: erasure-coding
> Reporter: Rakesh R
> Assignee: Rakesh R
> Priority: Minor
> Attachments: HDFS-9348-00.patch, HDFS-9348.branch-2.00.patch
>
>
> Presently calling {{dfs#getErasureCodingPolicy()}} on a non-existent file is
> returning the ErasureCodingPolicy info. As per the
> [discussion|https://issues.apache.org/jira/browse/HDFS-8777?focusedCommentId=14981077&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14981077]
> it has to validate and throw FileNotFoundException.
> Also, {{dfs#getEncryptionZoneForPath()}} API has the same behavior. Again we
> can discuss to add the file existence validation in this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
