[
https://issues.apache.org/jira/browse/NIFIREG-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745853#comment-16745853
]
Luke commented on NIFIREG-182:
------------------------------
I've just been bitten by this as well. The NiFi Registry project should clearly
state what it *cannot* do. The landing page
(https://nifi.apache.org/registry.html) explicitly tells you Registry is for
versioning flows, which gives the false impression it can:
* revert or delete a commit
* fork a tree
* merge changes from a fork into it's parent
In my case I copied a versioned flow, didn't realise the copy was also
versioned, made some changes and committed them, discovered a stateful
component didn't share state with the original and then discovered the original
(stable) version of the flow was now a commit behind.
I'll be destroying state history as well just to get over this, but I'm looking
at other ways of managing flow change history than through Nifi. Just not up to
snuff yet.
> Add a way to move on from reverted versions
> -------------------------------------------
>
> Key: NIFIREG-182
> URL: https://issues.apache.org/jira/browse/NIFIREG-182
> Project: NiFi Registry
> Issue Type: New Feature
> Affects Versions: 0.2.0
> Environment: NiFi 1.7.0, NiFi Registry 0.2.0
> Reporter: Fredrik Skolmli
> Priority: Minor
>
> Quote from {{nifi-users thread "Registry - deleting versions of flow}}".
> {quote}I'm not sure if my workflow needs to change using NiFi + NiFi
> Registry, or if this is a bug or corner-case.
>
> I do the following:
> 1) Create a new process group, make the initial flow and start version
> control (ver 1)
> 2) Modify the workflow and commit (ver 2)
> 3) Realize the most recent change was defective, and reverts (back to ver 1)
> 4) Make some new changes
>
> I'm now stuck with NiFi telling me "Local changes have been made and a newer
> version of the flow is available".
>
> There are two options as I see it:
>
> 1) The need for the ability to delete version 2, enabling me to commit my
> local changes.
> 2) The ability to commit a new version 3, which is a child of version 1.
>
> As of now (running NiFI 1.7 and Registry 0.2), my only options are to either
> revert my local changes or stop version control. My current workaround is
> unfortunately to stop version control, delete the entire flow using the
> Registry UI and start over again.
> Thoughts?
> {quote}
>
> Creating Jira ticket as suggested by [~bende] to track
> development/ideas/thoughts.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
