You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Rakesh R (JIRA)" <ji...@apache.org> on 2015/12/10 08:53:11 UTC
[jira] [Updated] (HDFS-9472) concat() API does not give proper
exception messages on ./reserved relative path
[ https://issues.apache.org/jira/browse/HDFS-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rakesh R updated HDFS-9472:
---------------------------
Summary: concat() API does not give proper exception messages on ./reserved relative path (was: concat() API does not resolve the .reserved path)
> concat() API does not give proper exception messages on ./reserved relative 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, HDFS-9472-01.patch, HDFS-9472-02.patch, HDFS-9472-03.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. The idea of this jira to discuss this behavior and handle accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)