[
https://issues.apache.org/jira/browse/MINIFICPP-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841214#comment-16841214
]
Mr TheSegfault commented on MINIFICPP-841:
------------------------------------------
[~krystyan] MiNiFi C++ only supports root process groups configured through
YAML. MiNiFI Java supports this because it and NiFi are the same underlying
engine.
You should see better results from the agent if you pull those processors up to
the root process group.
In general the approach of limiting them to the root group reduces complexity,
though the agent technically supports it, we don't allow that part to be
configured. In reviewing your config it seems that it would work without a
differentiated process group, but if that is required let me know and we can
open a ticket to explore adding that feature.
Further, i suspect your config will fail because not all processors are
supported in MiNiFi C++ without JNI features. JNI will allow all standard nar
processors to be run from the agent.
> agent does not do anything
> --------------------------
>
> Key: MINIFICPP-841
> URL: https://issues.apache.org/jira/browse/MINIFICPP-841
> Project: Apache NiFi MiNiFi C++
> Issue Type: Bug
> Affects Versions: 0.7.0
> Environment: Windows 10 - 64bits
> Compiled from Visual Studio 2017 - without JNI support
> Reporter: Christian Porzio
> Priority: Critical
> Labels: windows
> Attachments: krystyan_minifi-cpp.zip
>
>
> This is my first attempt to run minifi.exe cpp - I believe the compile is
> fine but I might be missing some config components.
> Basically when I launch that *minifi.exe* using a production _*config.yml*_
> that works with the java agent, nothing much seems to happen. I know it
> consumes my config.yml because if I create an error in it, now it complains
> about it.
> However when it runs nothing is being sent to my remote processor and none of
> the defined processor for that agent seem to be actually running.
> I have attached the whole runtime environment
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
