I don't believe I see any error messages on the initial remote process group
that gets created.
I do see the error message when I do a restart and there are existing remote
process groups but they do seem to connect eventually
It's only the initial create of the first remote process group
I develop in Java. Thinking of switching to Kotlin (rather than Scala).
Here is how the relevant code looks in my NifiRestClient, which uses Swagger
generated REST client to access NiFi REST API.
/*
* List all NiFi processors in this release
*/
public List
I would recommend ( if you want to do this ) looking at the source code for
the nar maven plugin, since you will have to re-implement it some how.
On November 15, 2018 at 18:19:36, Milan Das (m...@interset.com) wrote:
Trust me, you are bringing trouble. I am not sure if there is any user have
Hello,
It would really be best to use Maven as NiFi's NAR Maven plugin will
ensure that you are building the proper structure and will make things
easy for you.
Otherwise it would be up to you to somehow create the appropriate NAR
structure (and if it ever changes you would have to update your
Hi William,
> I do see the error message when I do a restart and there are existing remote
> process groups but they do seem to connect eventually
This is a known behavior for RPGs connecting to the same NiFi. During
start up process, RemoteProcessGroups try to get remote info before
NiFi API
Hi William
My experience with using the REST API to create RPG is that you must wait “some
time” before the port becomes available. A restart is not needed though.
My workaround is to repeatedly call GET on the RPG until the port becomes
available. It typically takes more than 10 seconds on a 5
