[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)
