[ 
https://issues.apache.org/jira/browse/MINIFICPP-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gábor Gyimesi resolved MINIFICPP-490.
-------------------------------------
    Resolution: Won't Fix

Nanofi is abandoned.

> Create common recipes based on the C & C2 api
> ---------------------------------------------
>
>                 Key: MINIFICPP-490
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-490
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Sub-task
>            Reporter: Marc Parisi
>            Priority: Major
>              Labels: CAPI
>
> Have building blocks defined so that we can easily chain functions to build 
> out a 'recipe'
> Ideas:
>  
> 1) Gather files ( usually logs ) from device, transmit to nifi through site 
> to site (highest need )
>     1.a) Search logs for trigger keywords , transmit a flowfile with 
> attributes reflecting when/how that trigger occurred. 
>  
> 2) Gather in memory data from device, transmit to nifi through site to site
>       Exists as an API component to give users the ability to store data 
> already captured and ship with guarantees
> 3) Ability to perform numeric analysis ( counts, sum, mean, average, – 
> aggregating information from flow files, etc ) on attributes, transmitting 
> results to NiFi
>      Key: Packets received Value: 1   across a time span, you want to know 
> how many packets received
>      Returns single flow file with combined or aggregated information   
>        * On vehicle, want to count the number of times speed exceeds 80 km/h 
> – only shipped once a day
>  
> 4) capture packets on a device, analyze statistics about packets, transmit to 
> nifi ( lower need )
>     a) Types of packets
>     b) Number of packets
>     c) Packets received over time ( effective speed )
>    ( Attributes are bags of words )
> 4) Explore persisting ( FlowFiles and content ) when the capability exists 
> and the consumer of the API wants to
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to