[jira] [Commented] (FLINK-17891) FlinkYarnSessionCli sets wrong execution.target type

[ https://issues.apache.org/jira/browse/FLINK-17891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114622#comment-17114622 ] Shangwen Tang commented on FLINK-17891: --- Hi [~lzljs3620320] [~jark] , Can you assi

[jira] [Commented] (FLINK-17891) FlinkYarnSessionCli sets wrong execution.target type

[ https://issues.apache.org/jira/browse/FLINK-17891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114251#comment-17114251 ] Shangwen Tang commented on FLINK-17891: --- This is a simple fix, assign this issue t

[jira] [Comment Edited] (FLINK-17891) FlinkYarnSessionCli sets wrong execution.target type

[ https://issues.apache.org/jira/browse/FLINK-17891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114246#comment-17114246 ] Shangwen Tang edited comment on FLINK-17891 at 5/22/20, 5:14 PM: -

[jira] [Comment Edited] (FLINK-17891) FlinkYarnSessionCli sets wrong execution.target type

[ https://issues.apache.org/jira/browse/FLINK-17891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114246#comment-17114246 ] Shangwen Tang edited comment on FLINK-17891 at 5/22/20, 5:14 PM: -

[jira] [Commented] (FLINK-17891) FlinkYarnSessionCli sets wrong execution.target type

[ https://issues.apache.org/jira/browse/FLINK-17891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114246#comment-17114246 ] Shangwen Tang commented on FLINK-17891: --- My idea is that if we start the flink ses

[jira] [Updated] (FLINK-17891) FlinkYarnSessionCli sets wrong execution.target type

[ https://issues.apache.org/jira/browse/FLINK-17891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shangwen Tang updated FLINK-17891: -- Description: I submitted a flink session job at the local YARN cluster, and I found that the

[jira] [Created] (FLINK-17891) FlinkYarnSessionCli sets wrong execution.target type

Shangwen Tang created FLINK-17891: - Summary: FlinkYarnSessionCli sets wrong execution.target type Key: FLINK-17891 URL: https://issues.apache.org/jira/browse/FLINK-17891 Project: Flink Issue

[jira] [Commented] (FLINK-16735) FlinkKafkaProducer should check that it is not null before sending a record

[ https://issues.apache.org/jira/browse/FLINK-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072818#comment-17072818 ] Shangwen Tang commented on FLINK-16735: --- Ok, thanks for your reply :D [~aljoscha]

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

[ https://issues.apache.org/jira/browse/FLINK-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072812#comment-17072812 ] Shangwen Tang commented on FLINK-16708: --- CC: [~lzljs3620320] [~jark] [~knaufk] Can

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

[ https://issues.apache.org/jira/browse/FLINK-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067653#comment-17067653 ] Shangwen Tang commented on FLINK-16708: --- CC: [~lzljs3620320] > When a JDBC connec

[jira] [Issue Comment Deleted] (FLINK-16708) When a JDBC connection has been closed, the retry policy of the JDBCUpsertOutputFormat cannot take effect

[ https://issues.apache.org/jira/browse/FLINK-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shangwen Tang updated FLINK-16708: -- Comment: was deleted (was: My opinion is that when jdbcWriter.executeBatch () throws an except

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

[ https://issues.apache.org/jira/browse/FLINK-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067329#comment-17067329 ] Shangwen Tang commented on FLINK-16708: --- I think we should check the connection wh

[jira] [Issue Comment Deleted] (FLINK-16708) When a JDBC connection has been closed, the retry policy of the JDBCUpsertOutputFormat cannot take effect

[ https://issues.apache.org/jira/browse/FLINK-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shangwen Tang updated FLINK-16708: -- Comment: was deleted (was: So when the connection is closed, the second retry of the flush met

[jira] [Issue Comment Deleted] (FLINK-16708) When a JDBC connection has been closed, the retry policy of the JDBCUpsertOutputFormat cannot take effect

[ https://issues.apache.org/jira/browse/FLINK-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shangwen Tang updated FLINK-16708: -- Comment: was deleted (was: On the first execution, connection.getAutoCommit () throws PSQLExce

[jira] [Updated] (FLINK-16708) When a JDBC connection has been closed, the retry policy of the JDBCUpsertOutputFormat cannot take effect

[ https://issues.apache.org/jira/browse/FLINK-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shangwen Tang updated FLINK-16708: -- Description: In our test environment, I used the tcpkill command to simulate a scenario where

[jira] [Updated] (FLINK-16708) When a JDBC connection has been closed, the retry policy of the JDBCUpsertOutputFormat cannot take effect

[ https://issues.apache.org/jira/browse/FLINK-16708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shangwen Tang updated FLINK-16708: -- Summary: When a JDBC connection has been closed, the retry policy of the JDBCUpsertOutputForma

[jira] [Comment Edited] (FLINK-16735) FlinkKafkaProducer should check that it is not null before sending a record

[ https://issues.apache.org/jira/browse/FLINK-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17065809#comment-17065809 ] Shangwen Tang edited comment on FLINK-16735 at 3/24/20, 2:16 PM: -

[jira] [Commented] (FLINK-16735) FlinkKafkaProducer should check that it is not null before sending a record

[ https://issues.apache.org/jira/browse/FLINK-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17065809#comment-17065809 ] Shangwen Tang commented on FLINK-16735: ---   When kafkaSchema.serialize return a nu

[jira] [Updated] (FLINK-16735) FlinkKafkaProducer should check that it is not null before sending a record

[ https://issues.apache.org/jira/browse/FLINK-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shangwen Tang updated FLINK-16735: -- Attachment: (was: image-2020-03-24-11-28-47-309.png) > FlinkKafkaProducer should check tha

[jira] [Updated] (FLINK-16735) FlinkKafkaProducer should check that it is not null before sending a record

[ https://issues.apache.org/jira/browse/FLINK-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shangwen Tang updated FLINK-16735: -- Description: In our user scenario, some users implemented the KafkaSerializationSchema and so

[jira] [Updated] (FLINK-16735) FlinkKafkaProducer should check that it is not null before sending a record

[ https://issues.apache.org/jira/browse/FLINK-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shangwen Tang updated FLINK-16735: -- Attachment: image-2020-03-24-11-40-22-143.png > FlinkKafkaProducer should check that it is not

[jira] [Updated] (FLINK-16735) FlinkKafkaProducer should check that it is not null before sending a record

[ https://issues.apache.org/jira/browse/FLINK-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shangwen Tang updated FLINK-16735: -- Attachment: (was: image-2020-03-24-11-25-47-898.png) > FlinkKafkaProducer should check tha

[jira] [Updated] (FLINK-16735) FlinkKafkaProducer should check that it is not null before sending a record

[ https://issues.apache.org/jira/browse/FLINK-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shangwen Tang updated FLINK-16735: -- Description: In our user scenario, some users implemented the KafkaSerializationSchema and so

[jira] [Updated] (FLINK-16735) FlinkKafkaProducer should check that it is not null before sending a record

[ https://issues.apache.org/jira/browse/FLINK-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shangwen Tang updated FLINK-16735: -- Component/s: (was: Connectors / JDBC) Connectors / Kafka > FlinkKafkaProd

[jira] [Updated] (FLINK-16735) FlinkKafkaProducer should check that it is not null before sending a record

[ https://issues.apache.org/jira/browse/FLINK-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shangwen Tang updated FLINK-16735: -- Attachment: image-2020-03-24-11-28-47-309.png > FlinkKafkaProducer should check that it is not

[jira] [Created] (FLINK-16735) FlinkKafkaProducer should check that it is not null before sending a record

Shangwen Tang created FLINK-16735: - Summary: FlinkKafkaProducer should check that it is not null before sending a record Key: FLINK-16735 URL: https://issues.apache.org/jira/browse/FLINK-16735 Project