[
https://issues.apache.org/jira/browse/OOZIE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099997#comment-13099997
]
Hadoop QA commented on OOZIE-326:
---------------------------------
tucu00 remarked:
Closed by a9a0236c1531ec36cff003279c128debd3d84e54 LauncherMapper should add
OOZIE_JOB/ACTION_ID to action configuration
> GH-515: LauncherMapper should add OOZIE_JOB/ACTION_ID to action configuration
> -----------------------------------------------------------------------------
>
> Key: OOZIE-326
> URL: https://issues.apache.org/jira/browse/OOZIE-326
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> LauncherMapper currently sets the OOZIE_JOB/ACTION_ID as Java system
> properties before invoking the Main class.
> In the case of Pig, because of Pig logic these properties get included in the
> job configurations of Pig MR jobs.
> Hive 0.6 has similar behavior. With Hive 0.7 this is not happening anymore.
> Having the OOZIE_JOB/ACTION_ID in the job.xml of the MR jobs launched by
> Pig/Hive/MR is useful for monitoring and tracking purposes.
> LauncherMapper should inject OOZIE_JOB/ACTION_ID properties in the action
> configuration in the setupLauncherInfo(), by doing this, the properties will
> be available for the MR jobs of Pig/Hive/MR/Streaming/etc....
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
