[
https://issues.apache.org/jira/browse/NIFI-9730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-9730:
-----------------------------
Priority: Blocker (was: Critical)
> When upgrading to 1.16 or importing a flow from an older version, NiFi shows
> local changes on each processor
> ------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-9730
> URL: https://issues.apache.org/jira/browse/NIFI-9730
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.16.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.16.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This issue does not affect any version of NiFi that has already been released.
> Version 1.16 of NiFi now exposes several options for retrying failed attempts
> for processors. Versioned Flows built against older versions of NiFi don't
> have these fields. As a result, it shows all of these changes as Local
> Modifications (e.g., Max Backoff Period changed from 'null' to '10 mins').
> We should ignore these changes when the comparison shows that a null value
> was changed to the default value.
> This means that any flow that's been checked out from registry cannot be
> updated to a different version because it has local modifications. And those
> local modifications can't be reverted. Because of this, marking the priority
> as BLOCKER.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
