[ https://issues.apache.org/jira/browse/NIFI-8844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Payne resolved NIFI-8844. ------------------------------ Resolution: Fixed This was addressed a while back. Not sure on exact version, but testing now against main (1.15.0-SNAPSHOT) it definitely allows for this functionality. > Add a way to move on from reverted versions > ------------------------------------------- > > Key: NIFI-8844 > URL: https://issues.apache.org/jira/browse/NIFI-8844 > Project: Apache NiFi > Issue Type: New Feature > Components: NiFi Registry > 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 (v8.3.4#803005)