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:39:52 GMT

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

Srikanth Sundarrajan commented on FALCON-647:

Extending workflow execution listener isn't an option firstly due to the fact that per process
customization isn't possible and secondly as you have rightly pointed due to isolation considerations.

Listening to JMS notifications, would require each process owner to implement a daemon to
listen and act on the message. The extensions that I am suggesting enables the user to extend
the default behavior customizable at a process level, while not affecting the stability or
scalability of the system. 

> 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