[
https://issues.apache.org/jira/browse/NIFI-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15627024#comment-15627024
]
Sam Hjelmfelt commented on NIFI-2973:
-------------------------------------
Bryan,
Thats what I was worried about. The dropdown is a nice feature, but it does
limit the flexibility.
One option might be to modify the controller service dropdown to have an EL
option for dynamic selection. It would preserve the existing functionality
while enabling dynamic, EL-based selection for all services on all processors.
Regardless, this would be a major change, so I can just create a custom
processor in the short term. This page provides a nice guide on using database
connection pooling services by name:
http://funnifi.blogspot.com/2016/04/sql-in-nifi-with-executescript.html
> Allow Dynamic Connection Pooling Service for ExecuteSQL
> -------------------------------------------------------
>
> Key: NIFI-2973
> URL: https://issues.apache.org/jira/browse/NIFI-2973
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Sam Hjelmfelt
>
> Currently, extracting data from multiple databases requires a
> RouteOnAttribute processor and one ExecuteSQL processor for each database
> server. If the "Database Connection Pooling Service" attribute could be set
> with EL, one ExecuteSQL processor could be used.
> In the ExecuteSQL processor, the connection is obtained in each OnTrigger
> execution anyway:
> 172: final DBCPService dbcpService =
> context.getProperty(DBCP_SERVICE).asControllerService(DBCPService.class);
> ...
> 192: final Connection con = dbcpService.getConnection();
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
