[
https://issues.apache.org/jira/browse/NIFIREG-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende resolved NIFIREG-165.
---------------------------------
Resolution: Fixed
Marking as resolved since the change on NiFi side is resolved.
> Changing the destination of a relation is not identified as "Local change" by
> NiFi registry
> -------------------------------------------------------------------------------------------
>
> Key: NIFIREG-165
> URL: https://issues.apache.org/jira/browse/NIFIREG-165
> Project: NiFi Registry
> Issue Type: Bug
> Affects Versions: 0.1.0
> Reporter: Rahul Soni
> Assignee: Pierre Villard
> Priority: Major
>
> When the destination of a relation is changed, the NiFi relation does not
> track it is a local change.
> In a sample scenario, I have the flow as GenerateFF -> UpdateAttribute1 with
> UpdateAttribute2 processor hanging alone.
> After I commit the flow to NiFi registry, and then change the flow to direct
> the output of GenerateFF processor to UpdateAttribute2, it is not identified
> as a change by the registry.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)