[
https://issues.apache.org/jira/browse/NIFI-13572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868488#comment-17868488
]
endzeit commented on NIFI-13572:
--------------------------------
I think this sounds like a reasonable approach and would improve user
experience. However, I'm strongly in the favour of keeping this configurable as
you've outlined. There might be use cases where users do not want to use the
latest version automatically and users should be able to opt-out.
> Option to switch to latest version when checking out versioned flow
> -------------------------------------------------------------------
>
> Key: NIFI-13572
> URL: https://issues.apache.org/jira/browse/NIFI-13572
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework, SDLC
> Reporter: Pierre Villard
> Priority: Major
>
> Consider a flow being developed when using NiFi version X. The versioned flow
> (regardless of the registry implementation) will reference version X for the
> components of the flow.
> Later, NiFi is upgraded to version Y and only has components with version Y.
> If checking out the versioned flow in NiFi, it'll automatically use version Y
> of the components even though the flow is referencing version X.
> Now consider, that a version Z of the components is added to NiFi (could be
> custom components for which a new version is deployed). If checking out the
> versioned flow, ghost components will be created because NiFi will not make a
> decision for switching the components from versions X to version Y or Z. It'd
> be then be required to manually go and change the version of the components
> (or use the CLI for that) and version a new version of the flow to avoid the
> same issue later on.
> While the current behavior is understandable, I think this provides a poor
> user experience and, in most scenarios, users would likely want to use latest
> version available when multiple are available.
> The proposal is to have a checkbox in the check out step (it should also be
> reflected with a flag in the corresponding CLI command), that would be
> checked by default to use the latest version of the components when multiple
> versions are available.
> This option should be made available in two places: when uploading a JSON
> flow definition and when checking out a versioned flow via a registry client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
