[
https://issues.apache.org/jira/browse/FLINK-20658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252554#comment-17252554
]
Kezhu Wang commented on FLINK-20658:
------------------------------------
hmm..., the proposal I posted above actually does not work either as
{{DriverManager.getConnection}} will filter out driver by caller's class
loader, that is if {{driverName}} is loaded by descendant class loader of
{{flink-connector-jdbc}}, it is not possible to get
{{DriverManager.getConnection}} work.
I will do experiment to verify this later. If it is true, we need postpone it
to another workaround/discussion/issue.
> 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)
