Noe Detore created NIFI-14416:
---------------------------------
Summary: PrimaryNodeOnly bug in Nifi 2.x
Key: NIFI-14416
URL: https://issues.apache.org/jira/browse/NIFI-14416
Project: Apache NiFi
Issue Type: Bug
Components: NiFi API
Affects Versions: 2.3.0
Reporter: Noe Detore
Absolutely, here's a cleaner and more Jira-friendly version of your ticket
description:
----
*Summary:*
NiFi 2.3 fails to load with flows created in earlier versions that use the
deprecated {{PrimaryNodeOnly}} scheduling strategy.
*Description:*
In NiFi 1.x, the {{PrimaryNodeOnly}} scheduling strategy was deprecated and
replaced with the {{{}ExecutionNode.PRIMARY{}}}. However, it appears that NiFi
2.3 does not properly handle flows created using the old {{PrimaryNodeOnly}}
strategy from versions prior to this change. When attempting to start the
server with such a flow, it fails with a {{FlowSynchronizationException}} due
to an unrecognized enum value.
*Error Message:*
{{ERROR [main] org.apache.nifi.web.server.JettyServer Failed to start Server
org.apache.nifi.controller.serialization.FlowSynchronizationException:
java.lang.IllegalArgumentException: No enum constant
org.apache.nifi.scheduling.SchedulingStrategy.PRIMARY_NODE_ONLY}}
*Expected Behavior:*
Flows created in earlier versions using the deprecated scheduling strategy
should be handled gracefully, possibly by automigrating to the newer
{{ExecutionNode.PRIMARY}} equivalent.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
