You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Randy Gelhausen (JIRA)" <ji...@apache.org> on 2016/10/03 14:50:20 UTC
[jira] [Created] (MINIFI-112) Support UpdateAttribute for
nifi-minifi-cpp
Randy Gelhausen created MINIFI-112:
--------------------------------------
Summary: Support UpdateAttribute for nifi-minifi-cpp
Key: MINIFI-112
URL: https://issues.apache.org/jira/browse/MINIFI-112
Project: Apache NiFi MiNiFi
Issue Type: Bug
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)