Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 4 Dec 2015 11:17:11 +0000 (UTC)
From: "Rakesh R (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12916544.1448601029000.270995.1449227831061@Atlassian.JIRA>
In-Reply-To: <JIRA.12916544.1448601029000@Atlassian.JIRA>
References: <JIRA.12916544.1448601029000@Atlassian.JIRA>
 <JIRA.12916544.1448601029196@arcas>
Subject: [jira] [Commented] (HDFS-9472) concat() API does not resolve the
 .reserved path
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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)