You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Rakesh R (JIRA)" <ji...@apache.org> on 2015/10/30 20:08:27 UTC

[jira] [Created] (HDFS-9348) DFS GetErasureCodingPolicy API on a non-existent file should be handled properly

Rakesh R created HDFS-9348:
------------------------------

             Summary: 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


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)