[
https://issues.apache.org/jira/browse/OOZIE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469230#comment-13469230
]
James Kinley commented on OOZIE-949:
------------------------------------
Hi Alejandro,
To override the launcher job name you do still have to use
{{oozie.launcher.mapred.job.name}}.
The reason I check for the existence of {{mapred.job.name}} when setting up the
launcher configuration is because in {{setupLauncherConf}}, and specifically
{{injectLauncherProperties}} which it calls, it sets {{mapred.job.name}} to
{{oozie.launcher.mapred.job.name}}.
All I am doing is checking whether this has been set in the configuration, if
it has do nothing else, if it hasn't set to the default -
{{oozie:launcher:T={0}:W={1}:A={2}:ID={3}}}
Because the launcher job creates its own configuration instance
{{mapred.job.name}} is not shared between the launcher and action so unless the
user explicitly sets them to the same name, they will be different.
> Allow the user to set 'mapred.job.name'
> ---------------------------------------
>
> Key: OOZIE-949
> URL: https://issues.apache.org/jira/browse/OOZIE-949
> Project: Oozie
> Issue Type: Improvement
> Components: action, core
> Affects Versions: 3.1.3
> Reporter: James Kinley
> Priority: Minor
> Labels: patch
> Fix For: trunk
>
> Attachments: OOZIE-949.patch, OOZIE-949-v2.patch, OOZIE-949-v3.patch
>
>
> Give user the ability to set {{mapred.job.name}} in their workflow job
> configuration and not have Oozie override it in
> {{JavaActionExecutor#submitLauncher()}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
