hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-10850) getEZForPath should NOT throw FNF
Date Thu, 29 Sep 2016 18:06:20 GMT

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

Andrew Wang updated HDFS-10850:
    Attachment: HDSF-10850.001.patch

Rakesh, hope you don't mind, but I spent a little time making a new patch based on the revert.
Besides reverting, I also updated the javadoc for HdfsAdmin and modified the test to assert
the "returns null for non-existent path" behavior.

> getEZForPath should NOT throw FNF
> ---------------------------------
>                 Key: HDFS-10850
>                 URL: https://issues.apache.org/jira/browse/HDFS-10850
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs
>    Affects Versions: 2.8.0
>            Reporter: Daryn Sharp
>            Assignee: Rakesh R
>            Priority: Blocker
>         Attachments: HDSF-10850.001.patch
> HDFS-9433 made an incompatible change to the semantics of getEZForPath.  It used to return
the EZ of the closest ancestor path.  It never threw FNF.  A common use of getEZForPath to
determining if a file can be renamed, or must be copied due to mismatched EZs.  Notably, this
has broken hive.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message