You can organize them by creating nested process groups to make it
more sane to manage

On Wed, Nov 11, 2015 at 10:13 AM, Darren Govoni <dar...@ontrenet.com> wrote:
> Thanks Joe.
>
> And it seems all the different flows would be seen on the one canvas, just
> not connected?
>
>
> On 11/11/2015 10:02 AM, Joe Witt wrote:
>>
>> Darren,
>>
>> A single NiFi instance (on one node or a cluster of 10+) can handle
>> *many* different flows.
>>
>> Thanks
>> Joe
>>
>> On Wed, Nov 11, 2015 at 10:00 AM, Darren Govoni <dar...@ontrenet.com>
>> wrote:
>>>
>>> Mark,
>>>     Thanks for the tips. Appreciate it.
>>>
>>> So when I run nifi on a single server. It is essentially "one flow"?
>>> If I wanted to have say 2 or 3 active flows, I would (reasonably) have to
>>> run more instances of nifi with appropriate
>>> configuration to not conflict. Is that right?
>>>
>>> Darren
>>>
>>>
>>> On 11/11/2015 09:54 AM, Mark Petronic 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
>>>
>>>
>

Reply via email to