falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pragya Mittal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1405) Oozie workflow should not fail if post-processing fails
Date Wed, 04 Nov 2015 06:46:27 GMT

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

Pragya Mittal commented on FALCON-1405:
---------------------------------------

[~ajayyadava] As discussed the patch will work fine once oozie JMS notifications are enabled(FALCON-1231),
since log mover failure exception does not effect post-processing action.

> 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