[
https://issues.apache.org/jira/browse/FLINK-17294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-17294:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Using "DataSource" instead of "DriverManager" to get connection in JDBC
> connector
> ---------------------------------------------------------------------------------
>
> Key: FLINK-17294
> URL: https://issues.apache.org/jira/browse/FLINK-17294
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / JDBC
> Reporter: Lijie Wang
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> I noticed that JDBC connector using DriverManager to get connection, but
> DataSource is encouraged now. We should using DataSource instead of
> DriverManager.
> About the DriverManager vs DataSource, see
> https://stackoverflow.com/questions/15198319/why-do-we-use-a-datasource-instead-of-a-drivermanager.
> Some implementations of DataSource maybe we can use : alibaba durid, apache
> dbcp
> And we should introduce connection pool to get more performance.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
