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

ASF GitHub Bot commented on NIFIREG-190:
----------------------------------------

Github user kevdoran commented on a diff in the pull request:

    https://github.com/apache/nifi-registry/pull/133#discussion_r209032885
  
    --- Diff: 
nifi-registry-provider-api/src/main/java/org/apache/nifi/registry/hook/EventHookProvider.java
 ---
    @@ -36,4 +36,18 @@
          */
         void handle(Event event) throws EventHookException;
     
    +    /**
    +     * Examines the values from the 'Event Whitelist X' properties in the 
hook provider definition to determine
    +     * if the Event should be invoked for this particular EventType
    --- End diff --
    
    'Event Whitelist X' property has been renamed in this commit to 
'Whitelisted Event Type '.


> Support for Event Whitelisting in the Registry Event Hooks
> ----------------------------------------------------------
>
>                 Key: NIFIREG-190
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-190
>             Project: NiFi Registry
>          Issue Type: New Feature
>    Affects Versions: 0.2.0
>            Reporter: Jeremy Dyer
>            Assignee: Jeremy Dyer
>            Priority: Major
>             Fix For: 0.3.0
>
>
> Today when an event hook is configured it will be invoked for all of the NiFi 
> Registry events. While a user can parse the arguments in the script and 
> manually write scripts which ignore certain events it makes more sense to 
> provide this event whitelisting the the registry itself.
> I propose adding a new property called something like "Event Whitelist" to 
> the current configuration logic. If this property is not present things 
> should continue to operate just as they do now, AKA the script is sent all of 
> the events, if the property is specified it should contain a comma delimited 
> list of events that the hook provider should be triggered for.
> This will be extremely useful when providers that do not provider any sort of 
> filtering logic like the script hook provider come along.



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

Reply via email to