Re: Nifi Registry with 3 Nifi Environments

2018-05-04 Thread Scott Howell
Joe, We are using the GetFTP processor with differing Timers. In Dev and Staging we are using a Time based Timer but in Production we use a CRON based timer because of customer requirements. Thanks, Scott > On May 4, 2018, at 9:11 AM, Joe Witt wrote: > > Scott > > Can you share more about

Re: Nifi Registry with 3 Nifi Environments

2018-05-04 Thread Joe Witt
Scott 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. Thanks On Fri, May 4, 2018 at 10:06 AM, Charlie Meyer wrote: > We solved th

Re: Nifi Registry with 3 Nifi Environments

2018-05-04 Thread Charlie Meyer
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 a

Nifi Registry with 3 Nifi Environments

2018-05-04 Thread Scott Howell
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 wo