nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Witt <>
Subject Re: Nifi Registry with 3 Nifi Environments
Date Fri, 04 May 2018 14:11:24 GMT

Can you share more about processors/styles that you find yourself
changing often?  I've not seen cases where this would be important
personally but with 250+ components I concede there may well be many
such cases.


On Fri, May 4, 2018 at 10:06 AM, Charlie Meyer
<> wrote:
> We solved this issue by having our flows in the registry be parameterized by
> leveraging the variable registry and using a swagger-generated api client
> set those variables at runtime.
> -Charlie
> On Fri, May 4, 2018 at 9:04 AM, Scott Howell <>
> wrote:
>> We are currently setting up our dev environment and using Nifi-Registy to
>> version control we discovered that changing the scheduling on the processors
>> causes version control to tell us that we need to commit our changes. With
>> having different scheduling between Dev, Staging, and Production it would be
>> nice to be able to not have to store the scheduling of processors in version
>> control. I was wondering if anyone had ideas on how we could get around
>> this. Currently I am creating three different GETFTP processors one for each
>> environment that are disabled depending on what environment the flow is in.
>> Scott

View raw message