You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Gilman (Jira)" <ji...@apache.org> on 2020/02/05 17:59:00 UTC

[jira] [Updated] (NIFI-6958) Disabled State in Registry (in Sub PG) breaks Flow Update on Nifi Side

     [ https://issues.apache.org/jira/browse/NIFI-6958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Gilman updated NIFI-6958:
------------------------------
    Affects Version/s: 1.11.0
                       1.11.1
               Status: Patch Available  (was: In Progress)

> Disabled State in Registry (in Sub PG) breaks Flow Update on Nifi Side
> ----------------------------------------------------------------------
>
>                 Key: NIFI-6958
>                 URL: https://issues.apache.org/jira/browse/NIFI-6958
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.11.1, 1.11.0, 1.10.0
>         Environment: Nifi 1.10.0, Nifi-Registry 0.5.0
>            Reporter: Silka Simmen
>            Assignee: Matt Gilman
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We run into an error, when trying to update or import a Flow on Nifi from Registry: "No Processor with ID X belongs to this Process Group"
> To reproduce the error above we save a flow into the Registry that contains a disabled processor in a sub process group:
>  * Process Group saved to Registry
>  ** Sub Process Group
>  *** Processor in Disabled State
> It seems that a flow cannot be updated or imported anymore on Nifi side as soon as it contains a disabled processor in a sub process group.
> We think this bug might be introduced by this feature implementation: https://issues.apache.org/jira/browse/NIFI-6025



--
This message was sent by Atlassian Jira
(v8.3.4#803005)