FYI, JIRA ticket created at https://issues.apache.org/jira/browse/NIFIREG-182
// Fredrik On Fri, Jun 29, 2018 at 1:41 PM Bryan Bende <[email protected]> wrote: > I think we need to implement what you described in option #2 which is > basically like a force push in git terminology. > > If you want to create a JIRA for that I think it is a good request. > > > On Jun 29, 2018, at 6:40 AM, Fredrik Skolmli <[email protected]> wrote: > > > > Hi everyone. > > > > 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? > > > > BR > > Fredrik > > > >
