[
https://issues.apache.org/jira/browse/NIFI-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15624069#comment-15624069
]
Bryan Bende commented on NIFI-2973:
-----------------------------------
A couple of things to consider here...
Currently when a PropertyDescriptor is marked with
identifiesControllerService(SomeService.class) the framework automatically does
a few things:
* Makes a drop down of the valid controller services of that type
* Enables jumping from the property in the processor's config to the controller
service config
* Handles some other framework logic when you enable/disable a CS and it asks
to handle referencing components (I think)
In order for it to support EL you would need it to be a text-box instead of a
drop-down, which means not using identifiesControllerService, which means the
things above don't work anymore and the user would have to cut and paste a UUID
for the correct CS into the processor's property.
> 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)
