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

ASF GitHub Bot commented on MINIFICPP-31:
-----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/nifi-minifi-cpp/pull/262


> Support UpdateAttribute for nifi-minifi-cpp
> -------------------------------------------
>
>                 Key: MINIFICPP-31
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-31
>             Project: NiFi MiNiFi C++
>          Issue Type: New Feature
>            Reporter: Randy Gelhausen
>            Assignee: Andrew Christianson
>            Priority: Major
>             Fix For: 0.5.0
>
>
> nifi-minifi-cpp agents can generate multiple "streams" of flowfiles.
> For instance, to monitor a host, nifi-minifi-cpp runs nmon, ps, netstat, and 
> gathers logfiles from applications.
> But, for a given flowfile, any downstream NiFi collectors wont have 
> visibility into the originating hostname, nor metadata about which "stream" 
> (ExecuteProcess(nmon), ExecuteProcess(ps), TailFile(app1), TailFile(app2)) 
> generated it.
> One solution is to use a separate InputPort for each stream. This works, but 
> burdens both the team working on agent flows, and the team managing the 
> collector- they have to be in concert.
> A simpler (better?) approach is to allow agent teams to tag flowfiles with 
> differentiating metadata via use of UpdateAttribute.



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

Reply via email to