Etienne,
I'm in the same boat as you. Currently using 1.9.2, and haven't upgraded yet,
so only know of variables. I'm also concerned about migrating processor groups,
as templates, from one environment to another, which cannot be done via NiFi
Registry due to different networks/companies/firewalls. Currently, the
variables are included as the part of the template, but unsure how the
parameter context will be involved in the template. As well, those
variables/parameters are now global, and not self-contained in a processor
group or template, so any processor group can use any parameter context on a
whim, rather than having to create/define it locally. I'm trying to plan out
time for investigating the newer versions, and how parameter contexts will need
to be used going forward.
John
On Tuesday, May 19, 2020, 08:01:58 AM EDT, Etienne Jouvin
<[email protected]> wrote:
Hum, did not see that, and because I am still using "old" (1.9.2) version
where parameters are not available.
But I understand like you
Le mar. 19 mai 2020 à 13:56, James <[email protected]> a écrit :
Hi
Thanks for the response.
According to this, it's not recommended:
https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#Variables
"Variables and the nifi.variable.registry.properties property will be removed
in a future release. As a result, it is highly recommended to switch to
Parameters."
Or am I thinking of the wrong thing?
thanks
On 2020/05/19 08:11:14, Etienne Jouvin <[email protected]> wrote:
> Hi.
>
> In this case why don't you use variables ?
>
> Etienne
>
>
> Le mar. 19 mai 2020 à 09:41, James <[email protected]> a écrit :
>
> > Hi
> >
> > For the life of me, I can't find anything related to exporting templates
> > to new systems/environments along with the parameters.
> >
> > I don't need the parameter values necessarily, but, importing a new
> > template and then needing to create the parameters manually while setting
> > them seems a little tedious. Is this only possible using a registry perhaps?
> >
> > Any guidance would be helpful.
> >
> > thanks
> >
>
