[ https://issues.apache.org/jira/browse/HDFS-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024209#comment-15024209 ]
Hudson commented on HDFS-9433: ------------------------------ FAILURE: Integrated in Hadoop-Hdfs-trunk #2573 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2573/]) HDFS-9433. DFS getEZForPath API on a non-existent file should throw (umamahesh: rev 411e2b2e7cd63273a3819f99a3275821dfbcc9ce) * hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/DFSClient.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirEncryptionZoneOp.java * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestEncryptionZones.java > 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)