You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2020/12/27 05:54:00 UTC

[jira] [Closed] (FLINK-20657) Migrate jdbc connection code of JdbcInputFormat, JdbcLookupFunction, JdbcRowDataLookupFunction to SimpleJdbcConnectionProvider

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

Jark Wu closed FLINK-20657.
---------------------------
    Resolution: Fixed

Fixed in master: 0c36b666094c01a96d341d2b0ee0b6863a6484e8


> Migrate jdbc connection code of JdbcInputFormat, JdbcLookupFunction, JdbcRowDataLookupFunction to SimpleJdbcConnectionProvider
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-20657
>                 URL: https://issues.apache.org/jira/browse/FLINK-20657
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / JDBC, Table SQL / Ecosystem
>    Affects Versions: 1.13.0
>            Reporter: Kezhu Wang
>            Assignee: Kezhu Wang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.13.0
>
>
> Currently, there are multiple places to establish jdbc connection, several of them were written before introducing of {{JdbcConnectionProvider}} in FLINK-15782. We need to migrate these classes for reasons:
> * Code reusability.
> * Circumvent pitfalls of {{DriverManager}} such as FLINK-19435 and possible [others|https://ci.apache.org/projects/tomcat/tomcat85/docs/jndi-datasource-examples-howto.html#DriverManager,_the_service_provider_mechanism_and_memory_leaks] in one place.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)