[jira] [Commented] (NIFI-9730) When upgrading to 1.16 or importing a flow from an older version, NiFi shows local changes on each processor

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-9730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499690#comment-17499690 ] 

ASF subversion and git services commented on NIFI-9730:
-------------------------------------------------------

Commit 9d3788ff05a9774bb79ef34ac648266981f3864c in nifi's branch refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9d3788f ]

NIFI-9730: Consider a change in value for retry-related fields from 'null' to the default value as an environmental change so that it's not flagged as a Local Modification, which would prevent users from updating the version of the Process Group that they are using

Signed-off-by: Joe Gresock <jg...@gmail.com>

This closes #5809.


> 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)