falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-647) Add hooks for extensions in Falcon Pre and Post Processing actions
Date Wed, 03 Sep 2014 04:31:51 GMT

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

Srikanth Sundarrajan commented on FALCON-647:

My thinking on this is that besides standard post processing needs of the Falcon system, some
additional steps can be optionally included by the users. The users should be able to declare
whether failure on their extensions should result in workflow failures or not. Isolation isn't
so much a concern as post processing & pre-processing steps are spawned in an independent
mapper as a java action and as such can't cause outage or issues with the Falcon or Oozie
system per se due to an user introduced error. 

Execution order has to be system action first, followed by user actions.

> Add hooks for extensions in Falcon Pre and Post Processing actions
> ------------------------------------------------------------------
>                 Key: FALCON-647
>                 URL: https://issues.apache.org/jira/browse/FALCON-647
>             Project: Falcon
>          Issue Type: Improvement
>          Components: oozie
>    Affects Versions: 0.6
>            Reporter: Venkatesh Seetharam
>              Labels: extensions
> Open up the pre-processing and post-processing for user space customization.

This message was sent by Atlassian JIRA

View raw message