Regarding Nifi always running. Yes, it stays running. It is effectively a service with a REST and Web UI. Closing the web UI does not have any effect on the running processors - just your visibility to them.
On Wed, Nov 11, 2015 at 9:54 AM, Mark Petronic <markpetro...@gmail.com> wrote: > Look in your Nifi conf directory. The active flow is there as an aptly > named .gz file. Guessing you could just rename that and restart Nifi > which would create a blank new one. Build up another flow, then you > could repeat the same "copy to new file name" and restore some other > one to continue on some previous flow/. I'm pretty new to Nifi, too, > so maybe there is another way. Also, you can create point-in-time > backups of your from from the "Settings" dialog in the DFM. There is a > link that shows up in there to click. It will copy your master flow gz > to your conf/archive directory. You can create multiple snapshots of > your flow to retain change history. I actually gunzip my backups and > commit them to Git for a more formal change history tracking > mechanism. > > Hope that helps. > > On Wed, Nov 11, 2015 at 9:45 AM, Darren Govoni <dar...@ontrenet.com> wrote: >> Hi again, >> Sorry for the noob questions. I am reading all the online material as >> much as possible. >> But what hasn't jumped out at me yet is how flows are managed? >> >> Are they saved, loaded, etc? I access my nifi and build a flow. Now I want >> to save it and work on another flow. >> Lastly, will the flow be running even if I exit the webapp? >> >> thanks for any tips. If I missed something obvious, regrets. >> >> D
