falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Narayan Periwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1405) Oozie workflow should not fail if post-processing fails
Date Wed, 09 Sep 2015 05:56:45 GMT

    [ https://issues.apache.org/jira/browse/FALCON-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736233#comment-14736233
] 

Narayan Periwal commented on FALCON-1405:
-----------------------------------------

[~peeyushb], The post-processing action is no different from user-action. Falcon does not
maintain any explicit logs for the user-action, so why differentiate just post-processing
action. By design, once Falcon submits the coord, users expect all logs to go to Oozie or
Hadoop.

Also, if the users are interested in getting the logs for post-processing, there is a falcon
log api which the user can query to get access to the logs.

> Oozie workflow should not fail if post-processing fails
> -------------------------------------------------------
>
>                 Key: FALCON-1405
>                 URL: https://issues.apache.org/jira/browse/FALCON-1405
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Pallavi Rao
>            Assignee: Narayan Periwal
>         Attachments: FALCON-1405-v0.patch, FALCON-1405-v1.patch
>
>
> Currently, even if the user workflow succeeds and post-processing fails, the workflow
is marked as failed.
> IMO, the post-processing should be an optional step. We should wire workflow to succeed
even if the post-processing fails. Especially, after FALCON-1231, we won't even depend on
post-processing for completion notification.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message