[
https://issues.apache.org/jira/browse/NIFI-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943714#comment-16943714
]
ASF subversion and git services commented on NIFI-5910:
-------------------------------------------------------
Commit 9c9f9c10a980342b57ae13f38239fd809578d822 in nifi's branch
refs/heads/master from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9c9f9c1 ]
NIFI-5910 Retain external service reference when already set to an existing
external service
This closes #3783.
Signed-off-by: Mark Payne <[email protected]>
> Upgrading versioned process group overwrites external service reference
> -----------------------------------------------------------------------
>
> Key: NIFI-5910
> URL: https://issues.apache.org/jira/browse/NIFI-5910
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
> Labels: SDLC
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Using two NiFi instances and one NiFi registry...
> 1) In NiFi 1:
> * Create a controller service at the root level
> * Create a process group with a processor that uses the service from the
> root level
> * Start version control
> 2) In NiFi 2:
> * Import the flow and see the processor has an invalid service reference
> * Create a service at root level and change processor to use that service
> * Notice no local changes to commit, this is correct
> 3) In NiFi 1:
> * Make a change to the processor, just move its position
> * Save version 2 of the flow to registry
> 4) In NiFi 2:
> * Upgrade the process group to version 2
> * Notice the service reference of the processor is reset back to the invalid
> reference
> If you did the same steps, but in step 3 you modify something else besides
> that processor, then when upgrading in NiFi 2 it retains the correct service
> reference. So it is only when the upgrade has changes to the processor with
> the external service reference.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
