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 <[email protected]> Sent: Thursday, February 13, 2020 9:20 AM To: [email protected] 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 <[email protected]> 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
