[
https://issues.apache.org/jira/browse/NIFI-16198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bob Paulin resolved NIFI-16198.
-------------------------------
Resolution: Won't Fix
Considering making derived values update in getActiveFlow with some handing on
start() for connectors so derived values can be refreshed by starting and
stopping connector.
> [Connectors] Exiting Troubleshooting mode does not re-apply configuration
> -------------------------------------------------------------------------
>
> Key: NIFI-16198
> URL: https://issues.apache.org/jira/browse/NIFI-16198
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Bob Paulin
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Exiting Troubleshooting restores only the side-effect-free authoritative
> flow. That skips the connector’s apply path, so any values derived at apply
> time were left unset and processors could stay invalid, blocking start.
> {{Instead endTroubleshooting()}} could be routed through {{{}applyUpdate{}}},
> so the flow is reinstated and derived state is recomputed.
> Â
> Unit and system tests cover that exit re-runs apply and the connector becomes
> valid and startable afterward.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
