[
https://issues.apache.org/jira/browse/HDFS-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G updated HDFS-9433:
--------------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.8.0
Status: Resolved (was: Patch Available)
I have committed this to trunk and branch-2. Thanks Rakesh.
> DFS getEZForPath API on a non-existent file should throw FileNotFoundException
> ------------------------------------------------------------------------------
>
> Key: HDFS-9433
> URL: https://issues.apache.org/jira/browse/HDFS-9433
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: encryption
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 2.8.0
>
> Attachments: HDFS-9433-00.patch, HDFS-9433-00.patch
>
>
> Presently {{dfs.getEZForPath()}} API is behaving differently for a
> non-existent normal file and non-existent ezone file:
> - If user pass a normal non-existent file then it will return null value. For
> example, {{Path("/nonexistentfile")}}
> - If user pass a non-existent file but which is under an existing encryption
> zone then it is returning the parent's encryption zone info. For example,
> {{Path("/ezone/nonexistentfile")}}
> Here the proposed idea is to unify the behavior by throwing
> FileNotFoundException. Please refer the discussion
> [thread|https://issues.apache.org/jira/browse/HDFS-9348?focusedCommentId=14983301&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14983301].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
