Quantcast

nifi.templats.directory

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

nifi.templats.directory

Mark Bean
In NiFi 1.x (as compared to 0.x), any templates are now stored directly in
the flow.xml.gz file. Is that correct?

If so, what is the purpose (if any) of the nifi.properties entry for
"nifi.templates.directory"? Should this property be deprecated/removed?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: nifi.templats.directory

Mark Payne
Mark,

That is correct - templates are now stored in the flow.xml.gz itself. Its only purpose now is
for backward compatibility. If you put a template into the templates directory, it will be loaded
and stored in the flow.xml.gz on startup. This allows us to migrate templates from 0.x to 1.x.
Otherwise, we would have lost all templates when migrating.

Thanks
-Mark


> On Apr 12, 2017, at 11:40 AM, Mark Bean <[hidden email]> wrote:
>
> In NiFi 1.x (as compared to 0.x), any templates are now stored directly in
> the flow.xml.gz file. Is that correct?
>
> If so, what is the purpose (if any) of the nifi.properties entry for
> "nifi.templates.directory"? Should this property be deprecated/removed?

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: nifi.templats.directory

Mark Bean
Excellent! This is a perfect example of some of the "insider information"
I'd like to see in the documentation. (See my other mailing list item.) I
just tested it out and worked like a charm!

Thanks for the insight.
Mark


On Wed, Apr 12, 2017 at 12:28 PM, Mark Payne <[hidden email]> wrote:

> Mark,
>
> That is correct - templates are now stored in the flow.xml.gz itself. Its
> only purpose now is
> for backward compatibility. If you put a template into the templates
> directory, it will be loaded
> and stored in the flow.xml.gz on startup. This allows us to migrate
> templates from 0.x to 1.x.
> Otherwise, we would have lost all templates when migrating.
>
> Thanks
> -Mark
>
>
> > On Apr 12, 2017, at 11:40 AM, Mark Bean <[hidden email]> wrote:
> >
> > In NiFi 1.x (as compared to 0.x), any templates are now stored directly
> in
> > the flow.xml.gz file. Is that correct?
> >
> > If so, what is the purpose (if any) of the nifi.properties entry for
> > "nifi.templates.directory"? Should this property be deprecated/removed?
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: nifi.templats.directory

Mark Bean
In reply to this post by Mark Payne
Mark,

I stand corrected. The template in ./conf/templates is not added to the
flow.xml.gz on restart. I confirmed this behavior in both 1.1.1 and 1.1.2.
Can you please re-verify?

These are the steps I took:
removed all templates from UI
restart nifi
verify no templates in flow.xml.gz
verify ./conf/templates is empty
add template to ./conf/templates
restart nifi
verify template exists in UI
>> template does NOT exists in flow.xml.gz

Thanks,
Mark

On Wed, Apr 12, 2017 at 12:28 PM, Mark Payne <[hidden email]> wrote:

> Mark,
>
> That is correct - templates are now stored in the flow.xml.gz itself. Its
> only purpose now is
> for backward compatibility. If you put a template into the templates
> directory, it will be loaded
> and stored in the flow.xml.gz on startup. This allows us to migrate
> templates from 0.x to 1.x.
> Otherwise, we would have lost all templates when migrating.
>
> Thanks
> -Mark
>
>
> > On Apr 12, 2017, at 11:40 AM, Mark Bean <[hidden email]> wrote:
> >
> > In NiFi 1.x (as compared to 0.x), any templates are now stored directly
> in
> > the flow.xml.gz file. Is that correct?
> >
> > If so, what is the purpose (if any) of the nifi.properties entry for
> > "nifi.templates.directory"? Should this property be deprecated/removed?
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: nifi.templats.directory

Mark Bean
Mark,

Can you please confirm whether the templates stored in ./conf/templates (or
some other location identified by "nifi.templates.directory") are imported
into flow.xml.gz on startup? I am not seeing this occur on my 1.1.2
instance.

Please advise.

Thanks,
Mark

On Thu, Apr 13, 2017 at 2:37 PM, Mark Bean <[hidden email]> wrote:

> Mark,
>
> I stand corrected. The template in ./conf/templates is not added to the
> flow.xml.gz on restart. I confirmed this behavior in both 1.1.1 and 1.1.2.
> Can you please re-verify?
>
> These are the steps I took:
> removed all templates from UI
> restart nifi
> verify no templates in flow.xml.gz
> verify ./conf/templates is empty
> add template to ./conf/templates
> restart nifi
> verify template exists in UI
> >> template does NOT exists in flow.xml.gz
>
> Thanks,
> Mark
>
> On Wed, Apr 12, 2017 at 12:28 PM, Mark Payne <[hidden email]> wrote:
>
>> Mark,
>>
>> That is correct - templates are now stored in the flow.xml.gz itself. Its
>> only purpose now is
>> for backward compatibility. If you put a template into the templates
>> directory, it will be loaded
>> and stored in the flow.xml.gz on startup. This allows us to migrate
>> templates from 0.x to 1.x.
>> Otherwise, we would have lost all templates when migrating.
>>
>> Thanks
>> -Mark
>>
>>
>> > On Apr 12, 2017, at 11:40 AM, Mark Bean <[hidden email]> wrote:
>> >
>> > In NiFi 1.x (as compared to 0.x), any templates are now stored directly
>> in
>> > the flow.xml.gz file. Is that correct?
>> >
>> > If so, what is the purpose (if any) of the nifi.properties entry for
>> > "nifi.templates.directory"? Should this property be deprecated/removed?
>>
>>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: nifi.templats.directory

Mark Payne
Mark,

Sorry, I wasn't entirely clear. They are not imported immediately into the flow.xml.gz. Rather,
they are loaded into the 'controller' and whenever the controller is saved (i.e., a change is made
to the flow) they should be persisted to the flow.xml.gz. So, for instance, if you loaded the flow,
then moved a processor to the left a few pixels that would trigger it to save the templates to
the flow.xml.gz.

Thanks
-Mark


> On Apr 19, 2017, at 10:27 AM, Mark Bean <[hidden email]> wrote:
>
> Mark,
>
> Can you please confirm whether the templates stored in ./conf/templates (or
> some other location identified by "nifi.templates.directory") are imported
> into flow.xml.gz on startup? I am not seeing this occur on my 1.1.2
> instance.
>
> Please advise.
>
> Thanks,
> Mark
>
> On Thu, Apr 13, 2017 at 2:37 PM, Mark Bean <[hidden email]> wrote:
>
>> Mark,
>>
>> I stand corrected. The template in ./conf/templates is not added to the
>> flow.xml.gz on restart. I confirmed this behavior in both 1.1.1 and 1.1.2.
>> Can you please re-verify?
>>
>> These are the steps I took:
>> removed all templates from UI
>> restart nifi
>> verify no templates in flow.xml.gz
>> verify ./conf/templates is empty
>> add template to ./conf/templates
>> restart nifi
>> verify template exists in UI
>>>> template does NOT exists in flow.xml.gz
>>
>> Thanks,
>> Mark
>>
>> On Wed, Apr 12, 2017 at 12:28 PM, Mark Payne <[hidden email]> wrote:
>>
>>> Mark,
>>>
>>> That is correct - templates are now stored in the flow.xml.gz itself. Its
>>> only purpose now is
>>> for backward compatibility. If you put a template into the templates
>>> directory, it will be loaded
>>> and stored in the flow.xml.gz on startup. This allows us to migrate
>>> templates from 0.x to 1.x.
>>> Otherwise, we would have lost all templates when migrating.
>>>
>>> Thanks
>>> -Mark
>>>
>>>
>>>> On Apr 12, 2017, at 11:40 AM, Mark Bean <[hidden email]> wrote:
>>>>
>>>> In NiFi 1.x (as compared to 0.x), any templates are now stored directly
>>> in
>>>> the flow.xml.gz file. Is that correct?
>>>>
>>>> If so, what is the purpose (if any) of the nifi.properties entry for
>>>> "nifi.templates.directory"? Should this property be deprecated/removed?
>>>
>>>
>>

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: nifi.templats.directory

Mark Bean
As of version 1.2.0, templates in the specified nifi.templates.directory
location are not available via the UI until NiFi is restarted. Is this
expected behavior? Or, as indicated previously, should the template(s) be
loaded whenever the controller is saved?


On Wed, Apr 19, 2017 at 12:31 PM, Mark Payne <[hidden email]> wrote:

> Mark,
>
> Sorry, I wasn't entirely clear. They are not imported immediately into the
> flow.xml.gz. Rather,
> they are loaded into the 'controller' and whenever the controller is saved
> (i.e., a change is made
> to the flow) they should be persisted to the flow.xml.gz. So, for
> instance, if you loaded the flow,
> then moved a processor to the left a few pixels that would trigger it to
> save the templates to
> the flow.xml.gz.
>
> Thanks
> -Mark
>
>
> > On Apr 19, 2017, at 10:27 AM, Mark Bean <[hidden email]> wrote:
> >
> > Mark,
> >
> > Can you please confirm whether the templates stored in ./conf/templates
> (or
> > some other location identified by "nifi.templates.directory") are
> imported
> > into flow.xml.gz on startup? I am not seeing this occur on my 1.1.2
> > instance.
> >
> > Please advise.
> >
> > Thanks,
> > Mark
> >
> > On Thu, Apr 13, 2017 at 2:37 PM, Mark Bean <[hidden email]>
> wrote:
> >
> >> Mark,
> >>
> >> I stand corrected. The template in ./conf/templates is not added to the
> >> flow.xml.gz on restart. I confirmed this behavior in both 1.1.1 and
> 1.1.2.
> >> Can you please re-verify?
> >>
> >> These are the steps I took:
> >> removed all templates from UI
> >> restart nifi
> >> verify no templates in flow.xml.gz
> >> verify ./conf/templates is empty
> >> add template to ./conf/templates
> >> restart nifi
> >> verify template exists in UI
> >>>> template does NOT exists in flow.xml.gz
> >>
> >> Thanks,
> >> Mark
> >>
> >> On Wed, Apr 12, 2017 at 12:28 PM, Mark Payne <[hidden email]>
> wrote:
> >>
> >>> Mark,
> >>>
> >>> That is correct - templates are now stored in the flow.xml.gz itself.
> Its
> >>> only purpose now is
> >>> for backward compatibility. If you put a template into the templates
> >>> directory, it will be loaded
> >>> and stored in the flow.xml.gz on startup. This allows us to migrate
> >>> templates from 0.x to 1.x.
> >>> Otherwise, we would have lost all templates when migrating.
> >>>
> >>> Thanks
> >>> -Mark
> >>>
> >>>
> >>>> On Apr 12, 2017, at 11:40 AM, Mark Bean <[hidden email]>
> wrote:
> >>>>
> >>>> In NiFi 1.x (as compared to 0.x), any templates are now stored
> directly
> >>> in
> >>>> the flow.xml.gz file. Is that correct?
> >>>>
> >>>> If so, what is the purpose (if any) of the nifi.properties entry for
> >>>> "nifi.templates.directory"? Should this property be
> deprecated/removed?
> >>>
> >>>
> >>
>
>
Loading...