[
https://issues.apache.org/jira/browse/NIFI-6684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935295#comment-16935295
]
Alessandro D'Armiento commented on NIFI-6684:
---------------------------------------------
Hello [~jamescheng], I took a look on the two processors.
Some of the features you ask are definetely possible, however, unfortunately
you are comparing two processors which relies on different versions of
commons-dbcp (that is, Hive3ConnectionPool uses an older implementation).
For this reason, in a minor update MAX_CONN_LIFETIME and
SOFT_MIN_EVICTABLE_IDLE_TIME could not be added. I am however working on
introducing MIN_IDLE, MAX_IDLE, EVICTION_RUN_PERIOD and MIN_EVICTABLE_IDLE_TIME
> Add more property to Hive3ConnectionPool
> ----------------------------------------
>
> Key: NIFI-6684
> URL: https://issues.apache.org/jira/browse/NIFI-6684
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: jamescheng
> Priority: Minor
> Attachments: PutHive3 enhance.png
>
>
> The Hive3ConnectionPool is similar with DBCPConnectionPool as both of them
> are using DBCP BasicDataSource. However, Hive3ConnectionPool doesn't provide
> some properties of what DBCPConnectionPool has. Such as "Minimum Idle
> Connections", "Max Idle Connections", "Max Connection Lifetime", "Time
> Between Eviction Runs", "Minimum Evictable Idle Time" and "Soft Minimum
> Evictable Idle Time".
> This improvement is try to provide more properties for developer to set.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
