[
https://issues.apache.org/jira/browse/NIFI-10676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gene Hynson updated NIFI-10676:
-------------------------------
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
was:
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.
> NiFi does not negotiate compatible versions when loading flow from cluster
> connection response
> ----------------------------------------------------------------------------------------------
>
> Key: NIFI-10676
> URL: https://issues.apache.org/jira/browse/NIFI-10676
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Flow Versioning
> Affects Versions: 1.17.0, 1.16.3
> Reporter: Gene Hynson
> Priority: Minor
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
