[
https://issues.apache.org/jira/browse/NIFI-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende updated NIFI-4763:
------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Versioned Flows show as dirty when component versions change
> ------------------------------------------------------------
>
> Key: NIFI-4763
> URL: https://issues.apache.org/jira/browse/NIFI-4763
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.5.0
> Reporter: Bryan Bende
> Assignee: Mark Payne
> Priority: Minor
> Fix For: 1.6.0
>
>
> While testing the 1.5.0 RC I happened to have an existing NiFi instance that
> was running the 1.5.0-SNAPSHOT version of the flow versioning PR, and had a
> bunch of example versioned flows. I upgraded this instance by replacing the
> lib directory with everything from the 1.5.0 RC.
> When I went to the UI I noticed all the versioned PGs were showing local
> changes. Looking at one of them it was because the local flow had upgraded
> all the component versions to 1.5.0, but the last version of that flow in the
> registry had the components at 1.5.0-SNAPSHOT.
> At this point you can try to rollback the local changes, but it can't really
> rollback because there are no more processors for 1.5.0-SNAPSHOT. You can
> save a new version of the flow with the new component versions and all is
> good.
> This won't really be an issue until the next release when folks have already
> been using 1.5.0 + registry for a while and upgrade to 1.6.0 (or whatever the
> next release is). We may want to ignore component version differences until
> sometime in the future when we have an extension registry.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
