[
https://issues.apache.org/jira/browse/NIFI-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende reopened NIFI-6028:
-------------------------------
Re-opening this ticket due to a NPE that can occur based on these changes.
Create an empty PG, start version control, add a processor, show local changes:
{code:java}
java.lang.NullPointerException: null
at
org.apache.nifi.web.api.dto.DtoFactory.createComponentDifferenceDtos(DtoFactory.java:2475)
at
org.apache.nifi.web.StandardNiFiServiceFacade.getLocalModifications(StandardNiFiServiceFacade.java:4389){code}
Will submit a PR shortly.
> Upgrading NiFi can put versioned flows into a conflict state
> ------------------------------------------------------------
>
> Key: NIFI-6028
> URL: https://issues.apache.org/jira/browse/NIFI-6028
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.7.1
> Reporter: Bryan Bende
> Assignee: Mark Payne
> Priority: Major
> Labels: SDLC
> Fix For: 1.10.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> When you upgrade NiFi, existing processors may have new properties and
> relationships. If any of those processors are part of a versioned flow then
> these changes will trigger a local modification indicating that a new version
> needs to be saved to registry to track the new properties or relationships.
> The issue is when you have multiple environments...
> * Start in dev with NiFi version X
> * Upgrade dev to NiFi version Y
> * Now commit versioned PGs in dev that had local changes
> * Go to staging and upgrade NiFi to version Y
> * The versioned PGs are now in conflict because there is an upgrade
> available, but there are local changes detected from upgrading NiFI, even
> though these are the same changes available in the upgrade
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
