You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Ryota Egashira (JIRA)" <ji...@apache.org> on 2014/08/26 21:17:58 UTC
[jira] [Updated] (OOZIE-1728) When an ApplicationMaster restarts,
it restarts the launcher job: DistCp followup
[ https://issues.apache.org/jira/browse/OOZIE-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryota Egashira updated OOZIE-1728:
----------------------------------
Assignee: Ryota Egashira (was: Robert Kanter)
> When an ApplicationMaster restarts, it restarts the launcher job: DistCp followup
> ---------------------------------------------------------------------------------
>
> Key: OOZIE-1728
> URL: https://issues.apache.org/jira/browse/OOZIE-1728
> Project: Oozie
> Issue Type: Sub-task
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Ryota Egashira
>
> In doing OOZIE-1722, we had not not add support for the DistCp action because there wasn't a good clean way to set the {{mapreduce.job.tags}} property on the job launched by DistCp that would work between all versions of Hadoop.
> The best solution would be to switch our version of Hadoop 1 to Hadoop 1.2.1 (OOZIE-1613), which would make DistCp v2 available in Hadoop 1. The signatures of DistCp's constructor (where we can pass the tags property in a Configuration) should then be same. We can then duplicate what DistCp.main(...) does.
> A more immediate solution would involve some ugly reflection based on different versions of Hadoop.
--
This message was sent by Atlassian JIRA
(v6.2#6252)