[
https://issues.apache.org/jira/browse/HDFS-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983301#comment-14983301
]
Uma Maheswara Rao G commented on HDFS-9348:
-------------------------------------------
Hi Rakesh, unifying the behaviors would be a good idea. Yeah, I think ECZone
related APIs behavior change would be a incompatible change. In my opinion,
doing something on nonexistent file would be users unexpected situations, so
letting user know about the file existence make sense to me. Do we also need to
check ECPolicy setting and ECZone getting APIs?
[~andrew.wang], [~hitliuyi], could you guys also comment what is your opinion
on this change?
> 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
> Reporter: Rakesh R
> Assignee: Rakesh R
> Priority: Minor
> Attachments: HDFS-9348-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)
