[
https://issues.apache.org/jira/browse/MINIFI-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726103#comment-15726103
]
bqiu commented on MINIFI-112:
-----------------------------
I looked a
http://www.soft-gems.net/index.php/tools/49-the-antlr4-c-target-is-here, it is
just a single person project to code the antlr C++. I am not sure how stable
the project is.
If you need to add dynamic attribute into flow. You can call bool
FlowFileRecord::addAttribute(std::string key, std::string value)
That new attribute will be serialized and deserialized over S2S.
Thanks.
Bin
> 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)
