Bryan Bende created NIFI-15008:
----------------------------------
Summary: Parameter change not taking affect in stopped/disabled
component
Key: NIFI-15008
URL: https://issues.apache.org/jira/browse/NIFI-15008
Project: Apache NiFi
Issue Type: Bug
Affects Versions: 2.6.0
Reporter: Bryan Bende
Assignee: Bryan Bende
When modifying a parameter context we calculate all the affected components,
and for any that are running/enabled, we stop/disable them, then apply the
context updates, and then restart/re-enable those components.
Part of starting/enable is to call reload on the component so it can realize
any changes to the classpath that may have occurred through property changes
(could be indirect through param value changes).
The problem is for a component that is affected, but stopped/disabled, they
won't be reloaded. If you went to configure one of these components and
performed Verification, the classpath of the component will be stale from the
before the parameter was modified.
Concrete example:
* Create param context "Test" with param `DB_DRIVER` with no value
* Create process group "Test" using this param context
* Create a DBCPConnectionPool filling in postgres url, postgres driver class,
and driver location as #\{DB_DRIVER}
* Click verify and it should say it can't find the driver
* Go back to parameter context and edit DB_DRIVER to point to the postgres
driver jar
* Go back to the service and perform verify, it will get the same error even
though the driver is now available
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
