[HDFS-9433] DFS getEZForPath API on a non-existent file should throw FileNotFoundException

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: encryption
• Target Version/s: 2.8.0
• Hadoop Flags: Incompatible change, Reviewed
• Release Note: Unify the behavior of dfs.getEZForPath() API when getting a non-existent normal file and non-existent ezone file by throwing FileNotFoundException
• Assignee: Rakesh Radhakrishnan
• Reporter: Rakesh Radhakrishnan
• Created: 16/Nov/15 18:46
• Updated: 19/Jan/17 19:30
• Resolved: 24/Nov/15 02:53

Description

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.

Issue Links

• breaks: HDFS-10850 getEZForPath should NOT throw FNF