Problem with variables in 1.14

[Eduardo Fontes <ed...@gmail.com>]

Hi all,

Can someone test a thing in NiFi 1.14?

1) Create a DBCPConnectionPool in a Process Group;
2) In property "Database Driver Location(s)"set any variable (existing or
not), like ${teste-var};
3) Click Apply

To me, the UI give error but save the value. If I commit this in NiFi
Registry, I can not import the flow.

Somebody tell me if this happens only with my system or not, please.

Thanks so much.
Eduardo Fontes

Re: Problem with variables in 1.14

[Eduardo Fontes <ed...@gmail.com>]

JIRA NIFI-9211

On Fri, Sep 10, 2021 at 7:52 AM Eduardo Fontes <ed...@gmail.com>
wrote:

> Hi Peter,
>
> Thanks for reply.
> I've tested it again and you are half-right. kkk
> 1) If I use a non-existing variable, a got error;
> 2) If I use an existing variable, it's ok, BUT;
> 3) If I use an existing variable AND commit the flow to the NiFi Registry,
> I can't import that flow anymore. I got same error as case #1;
> 4) If same case as #3, I can import a early version (without import
> problems), then "change version" to the problematic one, it works fine.
> Seems the issue is when creating new components with variable references in
> the import process, along with using non-existing variable in UI.
>
> I've tested with processors and other controller services, and with other
> properties in DBCPConnectionPool, but it seems to be a very specific issue
> with property "Database Driver Location(s)" in DBCPConnectionPool
> controller service.
> I'll open a JIRA for this.
>
> Thanks.
> Eduardo Fontes
>
> On Fri, Sep 10, 2021 at 5:21 AM Peter Turcsanyi <tu...@apache.org>
> wrote:
>
>> Hi Eduardo,
>>
>> I managed to replicate the issue with a non-existing variable reference
>> but
>> it properly works for me if the variable exists.
>> Could you please double check it on your side?
>>
>> The non-existing variable case is definitely an issue that could have been
>> brought in with NIFI-8206 or NIFI-8429 (further investigation needed to
>> identify the root cause).
>>
>> Regards,
>> Peter Turcsanyi
>>
>> On Thu, Sep 9, 2021 at 11:14 PM Eduardo Fontes <ed...@gmail.com>
>> wrote:
>>
>> > Hi all,
>> >
>> > Can someone test a thing in NiFi 1.14?
>> >
>> > 1) Create a DBCPConnectionPool in a Process Group;
>> > 2) In property "Database Driver Location(s)"set any variable (existing
>> or
>> > not), like ${teste-var};
>> > 3) Click Apply
>> >
>> > To me, the UI give error but save the value. If I commit this in NiFi
>> > Registry, I can not import the flow.
>> >
>> > Somebody tell me if this happens only with my system or not, please.
>> >
>> > Thanks so much.
>> > Eduardo Fontes
>> >
>>
>

Re: Problem with variables in 1.14

[Peter Turcsanyi <tu...@cloudera.com.INVALID>]

Hi Eduardo,

Thanks for the detailed test cases.
Actually, I did not test it with NiFi Registry but I will.

Also thanks for creating the jira. I will take care of it.

Peter

On Fri, Sep 10, 2021 at 12:52 PM Eduardo Fontes <ed...@gmail.com>
wrote:

> Hi Peter,
>
> Thanks for reply.
> I've tested it again and you are half-right. kkk
> 1) If I use a non-existing variable, a got error;
> 2) If I use an existing variable, it's ok, BUT;
> 3) If I use an existing variable AND commit the flow to the NiFi Registry,
> I can't import that flow anymore. I got same error as case #1;
> 4) If same case as #3, I can import a early version (without import
> problems), then "change version" to the problematic one, it works fine.
> Seems the issue is when creating new components with variable references in
> the import process, along with using non-existing variable in UI.
>
> I've tested with processors and other controller services, and with other
> properties in DBCPConnectionPool, but it seems to be a very specific issue
> with property "Database Driver Location(s)" in DBCPConnectionPool
> controller service.
> I'll open a JIRA for this.
>
> Thanks.
> Eduardo Fontes
>
> On Fri, Sep 10, 2021 at 5:21 AM Peter Turcsanyi <tu...@apache.org>
> wrote:
>
> > Hi Eduardo,
> >
> > I managed to replicate the issue with a non-existing variable reference
> but
> > it properly works for me if the variable exists.
> > Could you please double check it on your side?
> >
> > The non-existing variable case is definitely an issue that could have
> been
> > brought in with NIFI-8206 or NIFI-8429 (further investigation needed to
> > identify the root cause).
> >
> > Regards,
> > Peter Turcsanyi
> >
> > On Thu, Sep 9, 2021 at 11:14 PM Eduardo Fontes <eduardo.fontes@gmail.com
> >
> > wrote:
> >
> > > Hi all,
> > >
> > > Can someone test a thing in NiFi 1.14?
> > >
> > > 1) Create a DBCPConnectionPool in a Process Group;
> > > 2) In property "Database Driver Location(s)"set any variable (existing
> or
> > > not), like ${teste-var};
> > > 3) Click Apply
> > >
> > > To me, the UI give error but save the value. If I commit this in NiFi
> > > Registry, I can not import the flow.
> > >
> > > Somebody tell me if this happens only with my system or not, please.
> > >
> > > Thanks so much.
> > > Eduardo Fontes
> > >
> >
>

Re: Problem with variables in 1.14

[Eduardo Fontes <ed...@gmail.com>]

Hi Peter,

Thanks for reply.
I've tested it again and you are half-right. kkk
1) If I use a non-existing variable, a got error;
2) If I use an existing variable, it's ok, BUT;
3) If I use an existing variable AND commit the flow to the NiFi Registry,
I can't import that flow anymore. I got same error as case #1;
4) If same case as #3, I can import a early version (without import
problems), then "change version" to the problematic one, it works fine.
Seems the issue is when creating new components with variable references in
the import process, along with using non-existing variable in UI.

I've tested with processors and other controller services, and with other
properties in DBCPConnectionPool, but it seems to be a very specific issue
with property "Database Driver Location(s)" in DBCPConnectionPool
controller service.
I'll open a JIRA for this.

Thanks.
Eduardo Fontes

On Fri, Sep 10, 2021 at 5:21 AM Peter Turcsanyi <tu...@apache.org>
wrote:

> Hi Eduardo,
>
> I managed to replicate the issue with a non-existing variable reference but
> it properly works for me if the variable exists.
> Could you please double check it on your side?
>
> The non-existing variable case is definitely an issue that could have been
> brought in with NIFI-8206 or NIFI-8429 (further investigation needed to
> identify the root cause).
>
> Regards,
> Peter Turcsanyi
>
> On Thu, Sep 9, 2021 at 11:14 PM Eduardo Fontes <ed...@gmail.com>
> wrote:
>
> > Hi all,
> >
> > Can someone test a thing in NiFi 1.14?
> >
> > 1) Create a DBCPConnectionPool in a Process Group;
> > 2) In property "Database Driver Location(s)"set any variable (existing or
> > not), like ${teste-var};
> > 3) Click Apply
> >
> > To me, the UI give error but save the value. If I commit this in NiFi
> > Registry, I can not import the flow.
> >
> > Somebody tell me if this happens only with my system or not, please.
> >
> > Thanks so much.
> > Eduardo Fontes
> >
>

Re: Problem with variables in 1.14

[Peter Turcsanyi <tu...@apache.org>]

Hi Eduardo,

I managed to replicate the issue with a non-existing variable reference but
it properly works for me if the variable exists.
Could you please double check it on your side?

The non-existing variable case is definitely an issue that could have been
brought in with NIFI-8206 or NIFI-8429 (further investigation needed to
identify the root cause).

Regards,
Peter Turcsanyi

On Thu, Sep 9, 2021 at 11:14 PM Eduardo Fontes <ed...@gmail.com>
wrote:

> Hi all,
>
> Can someone test a thing in NiFi 1.14?
>
> 1) Create a DBCPConnectionPool in a Process Group;
> 2) In property "Database Driver Location(s)"set any variable (existing or
> not), like ${teste-var};
> 3) Click Apply
>
> To me, the UI give error but save the value. If I commit this in NiFi
> Registry, I can not import the flow.
>
> Somebody tell me if this happens only with my system or not, please.
>
> Thanks so much.
> Eduardo Fontes
>