This repository has been archived by the owner on Jan 6, 2018. It is now read-only.
LauncherMapper should add OOZIE_JOB/ACTION_ID to action configuration #515
Comments
|
Closed by a9a0236 LauncherMapper should add OOZIE_JOB/ACTION_ID to action configuration |
tucu00
added a commit
to brookwc/oozie
that referenced
this issue
Aug 1, 2011
…ID to action configuration
tucu00
added a commit
to brookwc/oozie
that referenced
this issue
Aug 17, 2011
…ID to action configuration
abayer
pushed a commit
to cloudera/oozie.old
that referenced
this issue
Jun 21, 2012
…ID to action configuration From: Alejandro Abdelnur <tucu00@gmail.com> git-svn-id: https://svn.apache.org/repos/asf/incubator/oozie/trunk@1168750 13f79535-47bb-0310-9956-ffa450edef68
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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....
The text was updated successfully, but these errors were encountered: