[
https://issues.apache.org/jira/browse/OOZIE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450491#comment-13450491
]
James Kinley commented on OOZIE-949:
------------------------------------
In {{MapReduceActionExecutor#end}} could we not just check for the existence of
the "oozie.action.newId.properties" file for the job? Can we even get hold of
this file here (i.e. how does the executor know where to look because the path
is not set in any configuration)?
Alternatively, if the new Hadoop job ID is propagated back to Oozie, could we
not just set a flag in the db? That way all {{MapReduceActionExecutor#end}} has
to do is check that the flag is true to know that the ID's were swapped?
Is this check even needed here? Shouldn't the launcher fail the action if it
cannot swap the ID's?
> 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
>
>
> 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
