You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/05 02:53:27 UTC

[jira] [Updated] (STORM-821) storm-jdbc create a connection provider interface to decouple from hikariCP being the only connection pool implementation that can be used.

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

Rick Kellogg updated STORM-821:
-------------------------------
    Component/s: storm-jdbc

> storm-jdbc create a connection provider interface to decouple from hikariCP being the only connection pool implementation that can be used.
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: STORM-821
>                 URL: https://issues.apache.org/jira/browse/STORM-821
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-jdbc
>    Affects Versions: 0.10.0
>            Reporter: Parth Brahmbhatt
>            Assignee: Parth Brahmbhatt
>            Priority: Minor
>             Fix For: 0.10.0
>
>
> The current implementation of storm-jdbc is couple with HikariCP configuration. We propose to remove this coupling by introducing a connectionProvider interface with a default HikariCP implementation. This will allow users to do their own connection pool management or chose a different connection pooling library. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)