[jira] [Resolved] (NIFI-2973) Allow Dynamic Connection Pooling Service for ExecuteSQL

["Matt Burgess (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess resolved NIFI-2973.
--------------------------------
    Fix Version/s: 1.7.0
       Resolution: Duplicate

Resolving as duplicate of NIFI-5229

> 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
>            Priority: Minor
>             Fix For: 1.7.0
>
>
> 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
(v8.3.4#803005)