- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Can use a select output as DBCPConnectionPool controller input?
- Labels:
-
Apache NiFi
Created ‎11-05-2018 08:42 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
Created ‎11-06-2018 04:04 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Created ‎11-06-2018 04:04 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
