Nifi-registry and upgrade Nifi environments

[Scott Howell <sc...@payitgov.com>]

I was wanting to reach out and find out how people are upgrading Nifi environments while still using the registry to upgrade flows.

We have a particular issue occurring between nifi environments and a process flow. We run three environments Dev, Staging, and Production. We are on a weekly upgrade path and currently we are running 1.7.1 in dev while staging and production are on 1.6.0. Using Nifi-Registry for Flow versioning is causing an issue currently between our dev and staging environments because the PutSFTP processor has additional fields in 1.7.1 that do not occur in 1.6.0.

So I guess I have two questions.

Should we be using granular flow versioning at the process group level and the lowest point. Because right now we us it fairly high up for grouped process groups?

How is everyone handling upgrades to their Nifi environments and how does that work with Nifi-Registry?


Scott

Re: Nifi-registry and upgrade Nifi environments

[Bryan Bende <bb...@gmail.com>]

Scott,

I would think that you would upgrade dev to the latest version, in
this case 1.7.1, then make sure all your flows are working properly
and commit any updates to the registry. For example any of the process
groups that involved PutSFTP would need to be committed because of the
new properties.

Then when you feel good about everything in dev, you first upgrade
staging to 1.7.1, then upgrade all your versioned process groups. This
time there shouldn't be anything to commit, just verifying everything
is working, then repeat this step on prod.

I think building a flow in an environment running version X and then
importing into an environment running version Y is a little bit risky
because you can't really be 100% sure that the flow behaves exactly
the same since the underlying code of each processor could be
different. Generally any processor provided by Apache NiFi shouldn't
make a drastic change in functionality between second digit releases,
so the risk may be low, but it is still different versions.

-Bryan

On Thu, Oct 4, 2018 at 12:50 PM Scott Howell <sc...@payitgov.com> wrote:
>
> I was wanting to reach out and find out how people are upgrading Nifi environments while still using the registry to upgrade flows.
>
> We have a particular issue occurring between nifi environments and a process flow. We run three environments Dev, Staging, and Production. We are on a weekly upgrade path and currently we are running 1.7.1 in dev while staging and production are on 1.6.0. Using Nifi-Registry for Flow versioning is causing an issue currently between our dev and staging environments because the PutSFTP processor has additional fields in 1.7.1 that do not occur in 1.6.0.
>
> So I guess I have two questions.
>
> Should we be using granular flow versioning at the process group level and the lowest point. Because right now we us it fairly high up for grouped process groups?
>
> How is everyone handling upgrades to their Nifi environments and how does that work with Nifi-Registry?
>
>
> Scott