Looks like this change was made in 1.9.0: https://issues.apache.org/jira/browse/NIFI-5812
On Thu, Feb 13, 2020 at 11:55 AM David Gallagher <dgallag...@cleverdevices.com> wrote: > > @Bryan Bende, to add to this it looks like 'All' was an option in 1.8.0 but > is no longer an option in 1.11.1. This is why it can't be reverted, it seems. > > Thanks, > > Dave > > -----Original Message----- > From: Bryan Bende <bbe...@gmail.com> > Sent: Thursday, February 13, 2020 10:24 AM > To: users@nifi.apache.org > Subject: Re: NiFi 1.8.0 to 1.11.1 upgrade issue > > Ok so your QA environment has been upgraded to 1.11.1 and there is an > existing flow that is now in a conflict state because it says there are local > changes for the new properties, but also says a new version is available from > what was committed to registry from the dev environment? > > Can you provider the exact message from Show Local Changes? > > Execution Node is actually not a property, it is part of the scheduling of > the processor. It looks like QueryDatabaseTable was changed somewhere in > there to have @PrimaryNodeOnly which means it can only be scheduled on the > primary node, and maybe you previously had it schedule on all nodes? > > On Thu, Feb 13, 2020 at 9:57 AM David Gallagher > <dgallag...@cleverdevices.com> wrote: > > > > Hi Bryan - > > > > The new version of the flow came from a development environment. Thinking > > back on it, I upgraded that development environment from 1.8 -> 1.11.1 > > first and committed the change described to the 0.2.0 registry. I then > > upgraded the registry to 0.5.0, made another change, and committed that so > > I could get a new version of the flow with 0.5 metadata. That flow version > > is what I'm trying to import into the QA environment below. > > > > Thanks, > > > > Dave > > > > -----Original Message----- > > From: Bryan Bende <bbe...@gmail.com> > > Sent: Thursday, February 13, 2020 9:20 AM > > To: users@nifi.apache.org > > Subject: Re: NiFi 1.8.0 to 1.11.1 upgrade issue > > > > Hello, > > > > Can you elaborate on what step 3 means? Where did this new version come > > from that was imported to registry? > > > > -Bryan > > > > On Thu, Feb 13, 2020 at 9:11 AM David Gallagher > > <dgallag...@cleverdevices.com> wrote: > > > > > > Hi – I’m currently converting our flows from 1.8.0 to 1.11.1, with a > > > parallel upgrade from registry 0.2.0 to registry 0.5.0. Currently stuck > > > due to this set of steps: > > > > > > > > > > > > Upgraded registry from 0.2.0 to 0.5.0 Upgraded NiFi from 1.8.0 to > > > 1.11.1 Imported a new version of a flow to the 0.5.0 registry > > > > > > > > > > > > It looks like the QueryDatabaseTable processor gained some new properties > > > (‘Execution Mode’ now has ALL and PRIMARY options). So, the flow is stuck > > > because both local changes and a new version of the flow (in the > > > registry) are available. I’ve tried reverting local changes, but the > > > changes are just put right back. If I accept the changes (i.e. commit > > > local), I’m getting an error warning saying that available upgrades will > > > be ignored. Is there a way out of this one? Barring that, is the > > > preferred method to upgrade NiFi first, commit changes to the registry, > > > and then upgrade the registry? > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Dave
