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

ASF subversion and git services commented on NIFI-6778:
-------------------------------------------------------

Commit 7c9d34f820ea063349f7405c31d5587a040eb779 in nifi's branch 
refs/heads/master from Yolanda M. Davis
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7c9d34f ]

NIFI-6778 - Added rules engine service api and Easy Rules Implementation

NIFI-6778 - added comments and component description annotations

NIFI-6778 - added license and notice details

NIFI-6778 - added additional details section and updated description of service

NIFI-6778 - fixed checkstyle error

NIFI-6778 - addressed review comments for documentation and description 
corrections

NIFI-6778 - added include-rules profile for assembly build

NIFI-6778 - add MVEL and ASM to license and notice

NIFI-6778 - switch to use Jackson for NiFi Rules Json deserialization

Signed-off-by: Matthew Burgess <[email protected]>

This closes #3824


> Rules Engine Controller Service with Default Easy Rules Implementation
> ----------------------------------------------------------------------
>
>                 Key: NIFI-6778
>                 URL: https://issues.apache.org/jira/browse/NIFI-6778
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Yolanda M. Davis
>            Assignee: Yolanda M. Davis
>            Priority: Major
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> Create a rules engine controller service in NiFi which would allow 
> processors, reporting tasks and/or other controller services to interrogate a 
> centralized engine for actions required given a certain set of data (or 
> facts).  The rules engine should leverage a rules file or database to fire 
> rules and either return the list of action or execute required actions.
> For a default implementation the EasyRules engine can be used however an 
> interface should be offered to allow other implementations.  An internal 
> Rule/Action API can also be created to provide a common representation for 
> rules and actions within NiFi. This would allow Actions to be received and 
> processed by callers or allow Rules to generated and fired dynamically if 
> needed. 
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to