You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Rakesh R (JIRA)" <ji...@apache.org> on 2015/11/16 19:47:10 UTC
[jira] [Created] (HDFS-9433) DFS getEZForPath API on a non-existent
file should throw FileNotFoundException
Rakesh R created HDFS-9433:
------------------------------
Summary: 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
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)