[
https://issues.apache.org/jira/browse/NIFI-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-1440:
------------------------------
Description: Currently, the definition of a Remote Process Group
(inputs/outputs, etc) is driven by the instance running at the target URI. They
are modeled both visually and structurally after local Process Groups. They
allow one NiFi instance to communicate with another as though it was a local
Process Group. In trying to keep as consistent as possible with local Process
Groups changing the target URI was never implemented. It's certainly a valid
use case as we already offer changing the target URI for various \*Http
Processors as well as changing available relationships for various RouteOn\*
Processors. (was: Currently, the definition of a Remote Process Group
(inputs/outputs, etc) is driven by the instance running at the target URI. They
are modeled both visually and structurally after local Process Groups. They
allow one NiFi instance to communicate with another as though it was a local
Process Group. In trying to keep as consistent as possible with local Process
Groups changing the target URI was never implemented. It's certainly a valid
use case as we already offer changing the target URI for various *Http
Processors as well as changing available relationships for various RouteOn*
Processors.)
> Allow Remote Process Group Target URI to change after creation
> --------------------------------------------------------------
>
> Key: NIFI-1440
> URL: https://issues.apache.org/jira/browse/NIFI-1440
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Core UI
> Reporter: Matt Gilman
> Priority: Minor
>
> Currently, the definition of a Remote Process Group (inputs/outputs, etc) is
> driven by the instance running at the target URI. They are modeled both
> visually and structurally after local Process Groups. They allow one NiFi
> instance to communicate with another as though it was a local Process Group.
> In trying to keep as consistent as possible with local Process Groups
> changing the target URI was never implemented. It's certainly a valid use
> case as we already offer changing the target URI for various \*Http
> Processors as well as changing available relationships for various RouteOn\*
> Processors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
