You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@oozie.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2011/09/10 05:29:11 UTC

[jira] [Closed] (OOZIE-326) GH-515: LauncherMapper should add OOZIE_JOB/ACTION_ID to action configuration

     [ https://issues.apache.org/jira/browse/OOZIE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik closed OOZIE-326.
----------------------------------

    Resolution: Fixed

> 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