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] [Commented] (HDFS-9472) concat() API does not resolve the .reserved path
Date Fri, 04 Dec 2015 11:17:11 GMT

    [ https://issues.apache.org/jira/browse/HDFS-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041433#comment-15041433
] 

Rakesh R commented on HDFS-9472:
--------------------------------

Thanks [~umamaheswararao] for the suggestions. If this is designed intentionally, then IMHO
would be good to throw InvalidPathException to the callers instead of FNFException. How about
something like,

{code}
    if (FSDirectory.isReservedRawName(target) && FSDirectory.isReservedInodesName(target))
{
       throw new InvalidPathException(target);
    }
 // Also, will validate srcs...
{code}

> concat() API does not resolve the .reserved path
> ------------------------------------------------
>
>                 Key: HDFS-9472
>                 URL: https://issues.apache.org/jira/browse/HDFS-9472
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Rakesh R
>            Assignee: Rakesh R
>         Attachments: HDFS-9472-00.patch
>
>
> dfs#concat() API doesn't resolve the {{/.reserved/raw}} path.  For example, if the input
paths of the form {{/.reserved/raw/ezone/a}} then this API doesn't work properly. IMHO will
discuss here to support this behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message