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-9433) DFS getEZForPath API on a non-existent file should throw FileNotFoundException
Date Tue, 17 Nov 2015 04:36:11 GMT

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

Rakesh R updated HDFS-9433:
---------------------------
    Status: Patch Available  (was: Open)

> 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
>         Attachments: 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)

Mime
View raw message