You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Lijie Wang (Jira)" <ji...@apache.org> on 2020/05/27 15:38:00 UTC
[jira] [Commented] (FLINK-16681) Jdbc JDBCOutputFormat and
JDBCLookupFunction PreparedStatement loss connection, if long time not
records to write.
[ https://issues.apache.org/jira/browse/FLINK-16681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17117857#comment-17117857 ]
Lijie Wang commented on FLINK-16681:
------------------------------------
Hi, [~jark], as mentioned in [this PR|https://github.com/apache/flink/pull/11499], [~shenlang] is concentrating on work and no free time to complete this issue.
I'm willing to take over and finish this work. Can you reassign it to me?
I can purpose a new PR later.
> Jdbc JDBCOutputFormat and JDBCLookupFunction PreparedStatement loss connection, if long time not records to write.
> --------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-16681
> URL: https://issues.apache.org/jira/browse/FLINK-16681
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / JDBC
> Reporter: LakeShen
> Assignee: LakeShen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0, 1.10.2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In my thought, jdbc connector is the one of most frequently used connector in flink . But maybe there is a problem for jdbc connector. For example, if there are no records to write or join with dim table for a long time , the exception will throw like this :
> java.sql.SQLException: No operations allowed after statement closed
> Because there are long time no records to write , the PreparedStatement loss the connection.
> If there is no other jira to solve this problem , can you assign this jira to me , I will try my best to solve it , thank you .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)