[
https://issues.apache.org/jira/browse/NIFI-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518438#comment-16518438
]
Bryan Bende commented on NIFI-5320:
-----------------------------------
The scenario is when there are more than two versions available, but none of
the available versions are the one in the template, or flow.xml, or flow from
registry.
For example, template says processors from v 1.3.0, but the available choices
are 1.5.0 and 1.6.0. In this case we can't know which one they wanted.
If only 1.6.0 was available, then we just change the version from 1.3.0 to
1.6.0 (this is how upgrades happen transparently) or if 1.3.0 was one of the
versions available then we have the versions that was asked for so it works.
The challenges with the proposed solutions are that there could be tons of
components that need their version selected so it could be quite cumbersome to
step through many screens selecting versions, and for auto-selecting we don't
really enforce a format for the version string so someone could make the new
version "abc" and we don't really know that abc is newer than "1.6.0".
The ultimate solution is when we have an extension registry and we detect a
version that is not found, then we go out and download it automatically from
the extension registry.
> Template instantiation failure when multiple component nar versions exist
> -------------------------------------------------------------------------
>
> Key: NIFI-5320
> URL: https://issues.apache.org/jira/browse/NIFI-5320
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.5.0
> Reporter: Matthew Clarke
> Priority: Minor
>
> NiFi allows users to load multiple versions of the same component nar.
> For example:
> nifi-scripting-nar:1.2.0
> nifi-scripting-nar:1.5.0
> -
> Once I have done this, if i try to instantiate a template to the canvas that
> has a processor from this nar bundle that is neither of these versions
> (nifi-scripting-nar:1.3.0), it will fail to instantiate the entire template.
> -
> This error is displayed to user:
> "Multiple versions of org.apache.nifi.processors.script.ExecuteScript exist.
> No exact match for org.apache.nifi:nifi-scripting-nar:1.3.0"
> -
> When there are not multiple nar versions, template instantiation works fine
> since NiFi will automatically select the current processor version.
> -
> NiFi should allow a user to instantiate a template in such a scenario by
> either:
> 1. Prompt user to select which of the available versions to use during
> instantiation.
> 2. Auto-select a new version (select most current version by default)
> -
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
