[jira] [Commented] (FLINK-16708) When a JDBC connection has been closed, the retry policy of the JDBCUpsertOutputFormat cannot take effect and may result in data loss

[ https://issues.apache.org/jira/browse/FLINK-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064207#comment-17064207 ] tangshangwen commented on FLINK-16708: -- My opinion is that when jdbcWriter.executeB

[jira] [Commented] (FLINK-16708) When a JDBC connection has been closed, the retry policy of the JDBCUpsertOutputFormat cannot take effect and may result in data loss

[ https://issues.apache.org/jira/browse/FLINK-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064205#comment-17064205 ] tangshangwen commented on FLINK-16708: -- Hi  [~trohrmann] . Could you help assign th

[jira] [Comment Edited] (FLINK-16708) When a JDBC connection has been closed, the retry policy of the JDBCUpsertOutputFormat cannot take effect and may result in data loss

[ https://issues.apache.org/jira/browse/FLINK-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064202#comment-17064202 ] tangshangwen edited comment on FLINK-16708 at 3/22/20, 8:29 AM: --

[jira] [Commented] (FLINK-16708) When a JDBC connection has been closed, the retry policy of the JDBCUpsertOutputFormat cannot take effect and may result in data loss

[ https://issues.apache.org/jira/browse/FLINK-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064203#comment-17064203 ] tangshangwen commented on FLINK-16708: -- So when the connection is closed, the secon

[jira] [Commented] (FLINK-16708) When a JDBC connection has been closed, the retry policy of the JDBCUpsertOutputFormat cannot take effect and may result in data loss

[ https://issues.apache.org/jira/browse/FLINK-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064202#comment-17064202 ] tangshangwen commented on FLINK-16708: -- On the first execution, connection.getAutoC

[jira] [Created] (FLINK-16708) When a JDBC connection has been closed, the retry policy of the JDBCUpsertOutputFormat cannot take effect and may result in data loss

tangshangwen created FLINK-16708: Summary: When a JDBC connection has been closed, the retry policy of the JDBCUpsertOutputFormat cannot take effect and may result in data loss Key: FLINK-16708 URL: https://issues

[jira] [Closed] (FLINK-12195) Incorrect resource time setting causes flink to fail to submit

[ https://issues.apache.org/jira/browse/FLINK-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen closed FLINK-12195. Resolution: Resolved > Incorrect resource time setting causes flink to fail to submit > --

[jira] [Commented] (FLINK-12195) Incorrect resource time setting causes flink to fail to submit

[ https://issues.apache.org/jira/browse/FLINK-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16819237#comment-16819237 ] tangshangwen commented on FLINK-12195: -- Thanks [~till.rohrmann]! > Incorrect resou

[jira] [Assigned] (FLINK-12195) Incorrect resource time setting causes flink to fail to submit

[ https://issues.apache.org/jira/browse/FLINK-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen reassigned FLINK-12195: Assignee: tangshangwen > Incorrect resource time setting causes flink to fail to submit >

[jira] [Updated] (FLINK-12195) Incorrect resource time setting causes flink to fail to submit

[ https://issues.apache.org/jira/browse/FLINK-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated FLINK-12195: - Description: We used Tencent COS(object storage is similar to s3) as defaultFS, and when we sub

[jira] [Updated] (FLINK-12195) Incorrect resource time setting causes flink to fail to submit

[ https://issues.apache.org/jira/browse/FLINK-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated FLINK-12195: - Description: We used Tencent cos(object storage is similar to s3) as defaultFS, and when we sub

[jira] [Updated] (FLINK-12195) Incorrect resource time setting causes flink to fail to submit

[ https://issues.apache.org/jira/browse/FLINK-12195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] tangshangwen updated FLINK-12195: - Description: We used Tencent cos as defaultFS, and when we submitted the job, we ran into a YAR

[jira] [Created] (FLINK-12195) Incorrect resource time setting causes flink to fail to submit

tangshangwen created FLINK-12195: Summary: Incorrect resource time setting causes flink to fail to submit Key: FLINK-12195 URL: https://issues.apache.org/jira/browse/FLINK-12195 Project: Flink