Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Can use a select output as DBCPConnectionPool controller input?

Solved Go to solution

Can use a select output as DBCPConnectionPool controller input?

New Contributor

Hi everyone,

does anyone know if exist any way to use a select dbname output as input ( DBCPConnectionPool name ),

I have 30 queries to execute on more than 100 db's and i like to avoid create 100 processors groups.

Regards

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Can use a select output as DBCPConnectionPool controller input?

Super Guru

@Gonzalo Salvia

If you are using NiFi-1.7 then you can dynamically select DBCP connection pools.

Refer to NiFi-5229 Jira addressing this improvement.

If you are following this way you need to configure/enable connection pool before using them and then using one ExecuteSQL processor we are going to select the connection pools dynamically based on the attribute.

If you are using previous versions of NiFi-1.7 then we need to specify schema name for each query

(or)

We need to use those many process groups

(or)

Keep an attribute to identify which execute sql processor it should go then use RouteOnAttribute processor to route the flowfiles to the respected execute sql processor.

1 REPLY 1

Re: Can use a select output as DBCPConnectionPool controller input?

Super Guru

@Gonzalo Salvia

If you are using NiFi-1.7 then you can dynamically select DBCP connection pools.

Refer to NiFi-5229 Jira addressing this improvement.

If you are following this way you need to configure/enable connection pool before using them and then using one ExecuteSQL processor we are going to select the connection pools dynamically based on the attribute.

If you are using previous versions of NiFi-1.7 then we need to specify schema name for each query

(or)

We need to use those many process groups

(or)

Keep an attribute to identify which execute sql processor it should go then use RouteOnAttribute processor to route the flowfiles to the respected execute sql processor.