[
https://issues.apache.org/jira/browse/NIFI-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247033#comment-17247033
]
Hsin-Ying Lee commented on NIFI-1440:
-------------------------------------
Hi [~mcgilman]
I have created the PR for this case
For the original procedure, when the RPG start transmit, it will compare the
protocol only. if protocol changed, it will discard the state from disk
If user change the URIs to another instance, RPG not only keep the old instance
but also add new instance to the state. the RPG will have two different
instance at same time and show the errors when transmission.
in order to check if user change the URIs, I stored addition information into
persistence files, this is used to check if the current target instance is
match with state persistence file in disk.
Thanks
> 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: Improvement
> Components: Core Framework, Core UI
> Reporter: Matt Gilman
> Assignee: Hsin-Ying Lee
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
