You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2012/10/03 22:24:07 UTC
[jira] [Commented] (OOZIE-949) Allow the user to set
'mapred.job.name'
[ https://issues.apache.org/jira/browse/OOZIE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468795#comment-13468795 ]
Alejandro Abdelnur commented on OOZIE-949:
------------------------------------------
James, I've just noticed that launcher job will also get the same name as the real job, this may be confusing for users and they will not know which one is their job and which one is the launcher.
I'm thinking that 'mapred.job.name' should only set the job name of the real job, the action. And we should not override the launcher job name.
> 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