[
https://issues.apache.org/jira/browse/MINIFI-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687713#comment-15687713
]
Jeremy Dyer commented on MINIFI-112:
------------------------------------
[~randerzander] this is a valuable feature indeed. I was looking over what it
make take to implement and believe there are a few higher level components
missing from the current implementation that would need to be present first.
Expression language support is the first one to come to mind. I think it would
make sense for us to tackle that first. I will file a JIRA for expression
language support and post that back here to make tracking easier.
> Support UpdateAttribute for nifi-minifi-cpp
> -------------------------------------------
>
> Key: MINIFI-112
> URL: https://issues.apache.org/jira/browse/MINIFI-112
> Project: Apache NiFi MiNiFi
> Issue Type: New Feature
> Components: C++, Core Framework
> Reporter: Randy Gelhausen
>
> 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
(v6.3.4#6332)
