Serious bug with variable handling?

[Mike Thomsen <mi...@gmail.com>]

I have a variable registry set up with a view environment-specific
variables. I use a symlink to switch between properties files when I need
NiFi to target one environment vs the other. After restarting NiFi, I
noticed that it hasn't actually changed the variables. The ones for the
test environment are still in there despite me changing the symlink to
point to the prod environment and a restart.

Am I doing something wrong or is this a bug?

Thanks,

Mike

Re: Serious bug with variable handling?

[Mike Thomsen <mi...@gmail.com>]

Disregard... Problem entirely on my end. I forgot to update the path when I
upgraded. I installed a new copy of NiFi, did a cp on all of the relevant
conf files and forgot to update the path in the variable registry line.

On Sun, Dec 17, 2017 at 6:20 PM, Mike Thomsen <mi...@gmail.com>
wrote:

> I tested with GenerateFlowFile. Even when I could see the link pointing to
> the production properties file, it was still holding that value. Weird part
> is I changed the test environment's value to a nonsense URL and it didn't
> pick that up. I'll keep looking.
>
> So you're sure that it's not stored anywhere?
>
> Thanks,
>
> Mike
>
> On Sun, Dec 17, 2017 at 6:14 PM, Joe Witt <jo...@gmail.com> wrote:
>
>> dropped dev list.  please post to one or the other for these.
>>
>> The values arent stored so if the same values exist after restart id
>> suspect an issue with the link.
>>
>> you could test this with a custom proc for example
>>
>> On Dec 17, 2017 5:47 PM, "Mike Thomsen" <mi...@gmail.com> wrote:
>>
>>> I have a variable registry set up with a view environment-specific
>>> variables. I use a symlink to switch between properties files when I need
>>> NiFi to target one environment vs the other. After restarting NiFi, I
>>> noticed that it hasn't actually changed the variables. The ones for the
>>> test environment are still in there despite me changing the symlink to
>>> point to the prod environment and a restart.
>>>
>>> Am I doing something wrong or is this a bug?
>>>
>>> Thanks,
>>>
>>> Mike
>>>
>>
>

Re: Serious bug with variable handling?

[Mike Thomsen <mi...@gmail.com>]

I tested with GenerateFlowFile. Even when I could see the link pointing to
the production properties file, it was still holding that value. Weird part
is I changed the test environment's value to a nonsense URL and it didn't
pick that up. I'll keep looking.

So you're sure that it's not stored anywhere?

Thanks,

Mike

On Sun, Dec 17, 2017 at 6:14 PM, Joe Witt <jo...@gmail.com> wrote:

> dropped dev list.  please post to one or the other for these.
>
> The values arent stored so if the same values exist after restart id
> suspect an issue with the link.
>
> you could test this with a custom proc for example
>
> On Dec 17, 2017 5:47 PM, "Mike Thomsen" <mi...@gmail.com> wrote:
>
>> I have a variable registry set up with a view environment-specific
>> variables. I use a symlink to switch between properties files when I need
>> NiFi to target one environment vs the other. After restarting NiFi, I
>> noticed that it hasn't actually changed the variables. The ones for the
>> test environment are still in there despite me changing the symlink to
>> point to the prod environment and a restart.
>>
>> Am I doing something wrong or is this a bug?
>>
>> Thanks,
>>
>> Mike
>>
>

Re: Serious bug with variable handling?

[Joe Witt <jo...@gmail.com>]

dropped dev list.  please post to one or the other for these.

The values arent stored so if the same values exist after restart id
suspect an issue with the link.

you could test this with a custom proc for example

On Dec 17, 2017 5:47 PM, "Mike Thomsen" <mi...@gmail.com> wrote:

> I have a variable registry set up with a view environment-specific
> variables. I use a symlink to switch between properties files when I need
> NiFi to target one environment vs the other. After restarting NiFi, I
> noticed that it hasn't actually changed the variables. The ones for the
> test environment are still in there despite me changing the symlink to
> point to the prod environment and a restart.
>
> Am I doing something wrong or is this a bug?
>
> Thanks,
>
> Mike
>