nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Toivo Adams (JIRA)" <>
Subject [jira] [Commented] (NIFI-322) New Database Connection Pooling Controller Service
Date Sun, 01 Mar 2015 21:27:04 GMT


Toivo Adams commented on NIFI-322:

Initial implementation
Needs more work but at least basic functionality should work.

1. It's unclear how to do properties configuration.
In future controller services configuration can be done using UI.
But does this mean controller-services.xml will go away?
Also allowing a property to depend on another greatly helps user do to configuration.
But such functionality is not available yet.

2. Currently Pool configuration parameters are mostly default values.
In production most certainly users want to fine tune pool behavior.
It's not very nice to hard code pool parameter values.
Also pool parameter values are fairly low level and 'end user' should not understand or care
about them. Database and system administrators are persons why will change pool parameter
values. It's unclear how? It is wise to have some separate configuration files or UI which
are only for administrators?

3. Currently only Apache Derby embedded database is tested.
At least one another database system should be tested as well, may be Postgres?

4. Service is not tested in NiFi UI using processors which will use Connection pooling service
as source of connections to database.


> New Database Connection Pooling Controller Service
> --------------------------------------------------
>                 Key: NIFI-322
>                 URL:
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Toivo Adams
>            Priority: Minor
>              Labels: controller
>         Attachments:,,,, NIFI-322_01mar2015.patch,,
> Often DataFlows contain many processors which deal with database - select, update or
delete different data in different tables. 
> Yet database is same and connection pooling helps to speed up connecting to database
(open connection is fairly expensive). Also configuration must be done only in one place.

> Database Connection Pooling Controller Service helps to solve this in consistent way.

> related
> : Add a JDBC Processor for executing arbitrary
SQL queries. 

This message was sent by Atlassian JIRA

View raw message