[
https://issues.apache.org/jira/browse/OOZIE-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343988#comment-15343988
]
abhishek bafna commented on OOZIE-2582:
---------------------------------------
We call {{LauncherMain#writeExternalChildIDs()}} in the finally block for Oozie
actions Main class. Previously, we were writing the data (launched job ids) to
output properties files only. When a launched action job completes
successfully, the external child id is set from
{{JavaActionExecutor#getActionData()}} as part of
{{JavaActionExecutor#check()}}.
The patch contains the changes to write the returned hadoop ids
{{LauncherMain#getHadoopJobIds()}} into the
{{LauncherMapper#ACTION_DATA_EXTERNAL_CHILD_IDS}} file. Because
{{JavaActionExecutor#check}} reads the property and set the external child for
completed actions. This approach should help to capture the external child id
for all the actions.
Also, contains the log filter changes for (Hive and Sqoop), to get the
application id as soon as it is submitted.
> Populating external child Ids for action failures
> -------------------------------------------------
>
> Key: OOZIE-2582
> URL: https://issues.apache.org/jira/browse/OOZIE-2582
> Project: Oozie
> Issue Type: Bug
> Components: core
> Reporter: abhishek bafna
> Assignee: abhishek bafna
> Attachments: OOZIE-2582-00.patch
>
>
> Currently Oozie external child ids are populated into workflow bean, when the
> job/action completes successfully. It should populate external child ids in
> case of job failures as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
