[
https://issues.apache.org/jira/browse/NIFI-8953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17390351#comment-17390351
]
ASF subversion and git services commented on NIFI-8953:
-------------------------------------------------------
Commit a466e714a0b4ad1c6acd088faf131610097ac9a1 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a466e71 ]
NIFI-8953: When Process Group's default flowfile expiration / backpressure
threshold change, note that as a flow difference
Signed-off-by: Pierre Villard <[email protected]>
This closes #5258.
> When Process Group's default backpressure or flowfile expiration changes from
> versioned flow, NiFi does not detect it as a local change
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-8953
> URL: https://issues.apache.org/jira/browse/NIFI-8953
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.14.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Minor
> Fix For: 1.15.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In 1.14, the ability was added to specify the default Backpressure Threshold
> and default FlowFile Expiration for connections at a Process Group level.
> Now, when I create a Process Group and start version control via the
> Registry, this value is saved. However, if I then change the value in my
> Process Group, NiFi does not notice this as a local difference and flag it.
> It still shows as if everything is unchanged. We need to detect this as a
> difference so that it's shown in the UI and can be reverted/committed, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
