nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Bende (JIRA)" <>
Subject [jira] [Commented] (NIFI-1964) Persist flow.xml.gz on start-up so root group id is persisted
Date Fri, 03 Jun 2016 13:46:59 GMT


Bryan Bende commented on NIFI-1964:

[~ozhurakousky] I think they are separate issues... this ticket is specific to when you start
a NiFi instance for the first time, it generates a UUID for the root group but hasn't written
the flow.xml.gz to disk yet, then you shutdown and start again, now it generates a new UUID
for the root group, and this will continue until someone finally accesses the UI and does
something, then it is saved and all is good. 

For some of the authorization changes, we need to access the root group id on start up, even
if its a brand new instance, and we need to know it won't change. 

Nothing related to templates here. Do you agree?

> Persist flow.xml.gz on start-up so root group id is persisted
> -------------------------------------------------------------
>                 Key: NIFI-1964
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Sub-task
>          Components: Core Framework
>            Reporter: Bryan Bende
>            Priority: Minor
>             Fix For: 1.0.0
> Currently the flow.xml.gz is only persisted after someone accesses the UI and takes an
action like adding a processor or component. This means that if you keep restarting NiFi without
touching the UI, it will generate a different root group id each time.
> For the authorization refactoring we need to be able to access the root group id on start
up and know that it is going to be consistent regardless of whether the UI has been accessed.
We should persist the initial flow.xml.gz after the root group id is generated.

This message was sent by Atlassian JIRA

View raw message