Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Can apache minifi dynamically transmit to different nifi urls?

Solved Go to solution

Can apache minifi dynamically transmit to different nifi urls?

Expert Contributor

Hi, i am working on a project and i am wondering if minifi can dynamically transmit data to a different url without restarting? Currently i am using a remote process group for bidirectional communication between the minifi device and nifi server. Thank you.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Can apache minifi dynamically transmit to different nifi urls?

Master Guru
@Roger Young

The Remote Process Group (RPG) is not designed for dynamic target URL assignment. It is designed to communicate with a target standalone of NiFi cluster. During that communication it learns about all currently connected nodes in a target Nifi cluster and retains the URLS for all those nodes so it can perform a load-balanced delivery of data. It the event RPG cannot get an updated listing form the target it will continue to try to delivery to the last known set of target nodes. Since the RPG was never intended to be used to delivery data to multiple independent target NiFi instances, the ideal of dynamic URL was never considered.

There are other NifI processors such as putHTTP and InvokeHTTP that can take NiFi Expression Language (EL) as input for the target URL.

Thank you,
Matt

View solution in original post

1 REPLY 1
Highlighted

Re: Can apache minifi dynamically transmit to different nifi urls?

Master Guru
@Roger Young

The Remote Process Group (RPG) is not designed for dynamic target URL assignment. It is designed to communicate with a target standalone of NiFi cluster. During that communication it learns about all currently connected nodes in a target Nifi cluster and retains the URLS for all those nodes so it can perform a load-balanced delivery of data. It the event RPG cannot get an updated listing form the target it will continue to try to delivery to the last known set of target nodes. Since the RPG was never intended to be used to delivery data to multiple independent target NiFi instances, the ideal of dynamic URL was never considered.

There are other NifI processors such as putHTTP and InvokeHTTP that can take NiFi Expression Language (EL) as input for the target URL.

Thank you,
Matt

View solution in original post

Don't have an account?
Coming from Hortonworks? Activate your account here