You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Kezhu Wang (Jira)" <ji...@apache.org> on 2020/12/20 15:31:00 UTC
[jira] [Commented] (FLINK-20658) Make sure jdbc connection is
established by target driver
[ https://issues.apache.org/jira/browse/FLINK-20658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252454#comment-17252454 ]
Kezhu Wang commented on FLINK-20658:
------------------------------------
It is a step to driver class customization discussed in FLINK-19435. I propose to change {{Class.forName(driverName)}} to {{Class.forName(driverName, true, Thread.currentThread().getContextClassLoader())}} also, it should solve one additional problem: class not found if {{flink-connector-jdbc}} resides in flink lib while {{driverName}} resides in application jars.
[~lzljs3620320] [~jark] [~roman_khachatryan] What do you think ? Could you mind assign this to me if above sounds good ?
> Make sure jdbc connection is established by target driver
> ---------------------------------------------------------
>
> Key: FLINK-20658
> URL: https://issues.apache.org/jira/browse/FLINK-20658
> Project: Flink
> Issue Type: New Feature
> Components: Connectors / JDBC, Table SQL / Ecosystem
> Affects Versions: 1.13.0
> Reporter: Kezhu Wang
> Priority: Major
>
> Currently, {{SimpleJdbcConnectionProvider.getConnection}} may return connection established by driver different from {{jdbcOptions.driverName}} if there are multiple driver implementations for same jdbc url exist in class path.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)