[NIFI-10676] NiFi does not negotiate compatible versions when loading flow from cluster connection response

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.17.0, 1.16.3
• Component/s: Flow Versioning
• Assignee: Unassigned
• Reporter: Gene Hynson
• Created: 20/Oct/22 16:48
• Updated: 14/Sep/23 17:33
• Resolved: 14/Sep/23 17:33

Description

When a NiFi node loads the flow configuration from a file, it uses `BundleUpdateStrategy.USE_SPECIFIED_OR_COMPATIBLE_OR_GHOST` to allow for compatible flow resources to be used when the specified ones are not found. But when a NiFi node joins a cluster and receives the flow configuration from the primary node via the connection response, it uses `
BundleUpdateStrategy.USE_SPECIFIED_OR_FAIL` which requires the specified flow resources to exist on the node for the flow sync to succeed.
 
NiFi should use `BundleUpdateStrategy.USE_SPECIFIED_OR_COMPATIBLE_OR_GHOST` in both of these scenarios so that the flow sync behavior is consistent regardless of how the flow definition is received by the node.

To avoid introducing any risk in the normal NiFi upgrade process, introduce this change as an "opt-in only" change that can be configured in nifi.properties

Issue Links

• is superceded by: NIFI-12016 Improve leniency for bundle compatibility to allow for rolling upgrades
• relates to: NIFI-11162 When upgrading, rolling restart nodes to avoid service interruption
• relates to: NIFI-12016 Improve leniency for bundle compatibility to allow for rolling upgrades
• links to: GitHub Pull Request #6560