[
https://issues.apache.org/jira/browse/HDFS-9472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052385#comment-15052385
]
Hudson commented on HDFS-9472:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #8954 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/8954/])
HDFS-9472. concat() API does not give proper exception messages on (umamahesh:
rev e363417e7b7abdd5d149f303f729ecf3e95ef8f3)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirConcatOp.java
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestHDFSConcat.java
> 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: Improvement
> Components: namenode
> Affects Versions: 2.7.1
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 2.8.0
>
> Attachments: HDFS-9472-00.patch, HDFS-9472-01.patch,
> HDFS-9472-02.patch, HDFS-9472-03.patch, HDFS-9472-04.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)
