[
https://issues.apache.org/jira/browse/FLINK-17294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088643#comment-17088643
]
Jark Wu commented on FLINK-17294:
---------------------------------
Thanks [~wanglijie95]. But I'm not sure what's the benefit can we get from the
connection pool?
Because from my point of view, every Flink Task should hold a separate long
standing connection. In Flink jobs (either batch or streaming), the connection
number is stable (=task number), and the connection is always in use. It's very
different from the traditional online applications.
> 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: Major
>
> 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.3.4#803005)
