[
https://issues.apache.org/jira/browse/FALCON-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724728#comment-14724728
]
Peeyush Bishnoi edited comment on FALCON-1373 at 9/1/15 5:03 AM:
-----------------------------------------------------------------
[~bvellanki] Patch looks good. Can we update the doc as well in which we
explicitly mention that user should not add Namenode FQDN in srcStagingPath or
in targetStagingPath while providing these attributes through Hive DR
properties or from UI. If by mistake user has also specified the Namenode FQDN,
copy job will fail. If it is possible to add the check for this in code, it
will be nice.
was (Author: peeyushb):
[~bvellanki] Patch looks good. Can we update the doc as well in which we
explicitly specify that user should not specify Namenode FQDN in srcStagingPath
or in targetStagingPath while providing these attributes. If by mistake user
has also specify the Namenode FQDN, copy job will fail. If it is possible to
add the check for this in code, it will be nice.
> HiveDR does not work when job is run on destination cluster
> ------------------------------------------------------------
>
> Key: FALCON-1373
> URL: https://issues.apache.org/jira/browse/FALCON-1373
> Project: Falcon
> Issue Type: Bug
> Components: replication
> Affects Versions: 0.7
> Reporter: Balu Vellanki
> Assignee: Balu Vellanki
> Labels: hivedr
> Attachments: FALCON-1373.patch
>
>
> This happens because the sourceStagingPaths used for DistCp of events from
> source to target does not have the fully qualified sourceNameNode as part of
> stagingPath uri.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
