You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Gabriel Orstadius-Bui (Jira)" <ji...@apache.org> on 2024/04/02 12:04:00 UTC

[jira] [Created] (NIFI-12992) Processor referencing controller service shown as invalid after switching to stateless execution engine

Gabriel Orstadius-Bui created NIFI-12992:
--------------------------------------------

             Summary: Processor referencing controller service shown as invalid after switching to stateless execution engine
                 Key: NIFI-12992
                 URL: https://issues.apache.org/jira/browse/NIFI-12992
             Project: Apache NiFi
          Issue Type: Bug
          Components: NiFi Stateless
    Affects Versions: 2.0.0-M2
            Reporter: Gabriel Orstadius-Bui


How to reproduce:
 # A processor and a controller service referenced by the processor are both within a process group using the standard execution engine. The controller service is disabled and the processor is therefore displayed as invalid in the diagram.
 # Switch the process group's execution engine to Stateless.
 # The processor is incorrectly still displayed as invalid in the diagram.
 # Quickly opening the processor's configurations will still display the processor as invalid within the pop-up dialog.
 # Waiting for a few seconds and then (re-)opening the processor's configurations will then correctly show the processor as valid (just stopped). Going back to the diagram will then also display the processor as valid.
 # (Switching back to standard will conversely incorrectly display the processor as valid until waiting for a few seconds and opening its configurations)

In other words, it seems as if there is a long window of time after switching execution engine in which NiFi does not take the new execution engine into consideration when validating processors.

Ideally, the validation should correctly validate the processors right after switching the execution engine and display them as valid/invalid accordingly in the diagram.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)