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

Posted to issues@beam.apache.org by "Alexey Romanenko (JIRA)" <ji...@apache.org> on 2019/04/11 12:54:00 UTC

[jira] [Resolved] (BEAM-7041) JdbcIO should not wrap the provided datasource if it's already a pollable one

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

Alexey Romanenko resolved BEAM-7041.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.13.0

> JdbcIO should not wrap the provided datasource if it's already a pollable one
> -----------------------------------------------------------------------------
>
>                 Key: BEAM-7041
>                 URL: https://issues.apache.org/jira/browse/BEAM-7041
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-jdbc
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 2.13.0
>
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> Currently, {{JdbcIO}} systematically wrap the provided {{DataSource}} as a DBCP Poolable DataSource (in the {{JdbcIO#buildDataSource()}}).
> If the user provided DataSource is already a pollable datasource, it doesn't leverage the actual pool. The user should "control" if he wants a wrapped pollable datasource or directly the one he provides.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)