You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 07:17:10 UTC
[jira] [Created] (OOZIE-326) GH-515: 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
[jira] [Closed] (OOZIE-326) GH-515: LauncherMapper should add
OOZIE_JOB/ACTION_ID to action configuration
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (OOZIE-326) GH-515: LauncherMapper should add
OOZIE_JOB/ACTION_ID to action configuration
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ 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