You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (Jira)" <ji...@apache.org> on 2021/07/28 15:48:00 UTC
[jira] [Updated] (NIFI-8953) When Process Group's default
backpressure or flowfile expiration changes from versioned flow, NiFi does
not detect it as a local change
[ https://issues.apache.org/jira/browse/NIFI-8953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Payne updated NIFI-8953:
-----------------------------
Assignee: Mark Payne
Status: Patch Available (was: Open)
> 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
>
> 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)