[
https://issues.apache.org/jira/browse/HDFS-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497929#comment-14497929
]
Hudson commented on HDFS-8151:
------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk #2097 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/2097/])
HDFS-8151. Always use snapshot path as source when invalid snapshot names are
used for diff based distcp. Contributed by Jing Zhao. (jing9: rev
4c097e473bb1f18d1510deb61bae2bcb8c156f18)
*
hadoop-tools/hadoop-distcp/src/main/java/org/apache/hadoop/tools/DistCpSync.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-tools/hadoop-distcp/src/test/java/org/apache/hadoop/tools/TestDistCpSync.java
> Always use snapshot path as source when invalid snapshot names are used for
> diff based distcp
> ---------------------------------------------------------------------------------------------
>
> Key: HDFS-8151
> URL: https://issues.apache.org/jira/browse/HDFS-8151
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: distcp
> Affects Versions: 2.7.0
> Reporter: Sushmitha Sreenivasan
> Assignee: Jing Zhao
> Priority: Minor
> Fix For: 2.7.1
>
> Attachments: HDFS-8151.000.patch
>
>
> This is a bug reported by [~ssreenivasan]:
> HDFS-8036 makes the diff-based distcp use snapshot path as the source. This
> should also happen when
> # invalid snapshot names are provided as distcp parameters thus the diff
> report computation on the target cluster fails
> # there is modification happening in the target cluster thus
> {{checkNoChange}} returns false
> In other cases like source and target FS are not DistributedFileSystem, we
> should throw exceptions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
