hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh R (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-9348) DFS GetErasureCodingPolicy API on a non-existent file should be handled properly
Date Fri, 13 Nov 2015 12:19:10 GMT

     [ https://issues.apache.org/jira/browse/HDFS-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rakesh R updated HDFS-9348:
---------------------------
    Attachment: HDFS-9348.branch-2.00.patch

> 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
>          Components: erasure-coding
>            Reporter: Rakesh R
>            Assignee: Rakesh R
>            Priority: Minor
>         Attachments: HDFS-9348-00.patch, HDFS-9348.branch-2.00.patch
>
>
> 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)

Mime
View raw message