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

ASF GitHub Bot commented on GRIFFIN-200:
----------------------------------------

GitHub user toyboxman opened a pull request:

    https://github.com/apache/incubator-griffin/pull/444

    Define griffin plain-vanilla hook.

    the purpose of hook is for integration with components outside. Griffin 
would offer information about internal task status.
    
    Task: GRIFFIN-200

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/toyboxman/incubator-griffin hook

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-griffin/pull/444.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #444
    
----
commit 2fbd30a64c563febe59240b67aae4653e996a522
Author: Eugene <liujin@...>
Date:   2018-10-22T14:12:38Z

    Define griffin plain-vanilla hook.
    
    the purpose of hook is for integration with components outside. Griffin 
would offer information about internal task status.
    
    Task: GRIFFIN-200

----


> Lifecycle hooks support
> -----------------------
>
>                 Key: GRIFFIN-200
>                 URL: https://issues.apache.org/jira/browse/GRIFFIN-200
>             Project: Griffin (Incubating)
>          Issue Type: New Feature
>            Reporter: Nikolay Sokolov
>            Assignee: William Guo
>            Priority: Minor
>
> In some environments, users might want to perform certain actions 
> before/after job is created, before/after job is activated, before/after job 
> is deleted, and so on.
> To fullfill that need, some hook plugin mechanism can be provided, similar to 
> what Hive is doing. User would place respective jar files into Service module 
> classpath at deployment time, and would specify class names using some 
> annotation or using property listing class names (particular mechanism is yet 
> to be determined).
> Proposed signature:
> {code:none}
> public interface GriffinHook {
>     void onEvent(GriffinHookEvent event) throws Exception;
> }
> public interface GriffinHookEvent { ... }
> public interface JobEvent implements GriffinHookEvent { ... } 
> public class BeforeJobCreated implements JobEvent { ... }
> public class AfterJobCreated implements JobEvent { ... }
> public class BeforeJobDeleted implements JobEvent { ... }
> public class AfterJobDeleted implements JobEvent { ... }
> public interface JobInstanceEvent implements GriffinHookEvent { ... }
> public class BeforeJobInstanceStart implements JobInstanceEvent { ... }
> public class AfterJobInstanceEnd implements JobInstanceEvent { ... }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to