You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by John Fak <jo...@gmail.com> on 2019/10/04 20:12:50 UTC
DBCPConnectionPoolLookup
Does someone have a basic example of using this ?
I really dont understand it. And it seems useful.
Does the attribute database.name tie back to the "Name" of the
DBCPConnectionPool ?
How do you pass that dynamically ? Via some updateattibute processor ?
Be great to see a very basic flow on connecting to two or more sources
dynamically.
Re: DBCPConnectionPoolLookup
Posted by John Fak <jo...@gmail.com>.
Awesome.... I'll try it next week and if I can get it to work I'll let you
know
Thx !!!
On Fri, Oct 4, 2019, 6:24 PM Peter Turcsanyi <tu...@cloudera.com> wrote:
> Hi John,
>
> You need to add dynamic properties to DBCPConnectionPoolLookup controller
> service. The name of the property corresponds to database.name attribute,
> the value is the DBCPConnectionPool that can be looked up (by the name of
> the property).
> So the attribute database.name ties back to the name of the dynamic
> property, not to the name of the DBCPConnectionPool component.
>
> Please find attached my simple example. It contains only one
> DBCPConnectionPool that can be looked up, but a second one can be added in
> the same way.
>
> Regards,
> Peter Turcsanyi
>
> On Fri, Oct 4, 2019 at 10:13 PM John Fak <jo...@gmail.com> wrote:
>
>> Does someone have a basic example of using this ?
>> I really dont understand it. And it seems useful.
>>
>> Does the attribute database.name tie back to the "Name" of the
>> DBCPConnectionPool ?
>>
>> How do you pass that dynamically ? Via some updateattibute processor ?
>>
>> Be great to see a very basic flow on connecting to two or more sources
>> dynamically.
>>
>>
>>
>>
Re: DBCPConnectionPoolLookup
Posted by Peter Turcsanyi <tu...@cloudera.com>.
Hi John,
You need to add dynamic properties to DBCPConnectionPoolLookup controller
service. The name of the property corresponds to database.name attribute,
the value is the DBCPConnectionPool that can be looked up (by the name of
the property).
So the attribute database.name ties back to the name of the dynamic
property, not to the name of the DBCPConnectionPool component.
Please find attached my simple example. It contains only one
DBCPConnectionPool that can be looked up, but a second one can be added in
the same way.
Regards,
Peter Turcsanyi
On Fri, Oct 4, 2019 at 10:13 PM John Fak <jo...@gmail.com> wrote:
> Does someone have a basic example of using this ?
> I really dont understand it. And it seems useful.
>
> Does the attribute database.name tie back to the "Name" of the
> DBCPConnectionPool ?
>
> How do you pass that dynamically ? Via some updateattibute processor ?
>
> Be great to see a very basic flow on connecting to two or more sources
> dynamically.
>
>
>
>