You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Deblock (Jira)" <ji...@apache.org> on 2020/02/07 12:57:00 UTC
[jira] [Updated] (KAFKA-9522) kafka-connect failed when the topic
can not be accessed
[ https://issues.apache.org/jira/browse/KAFKA-9522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deblock updated KAFKA-9522:
---------------------------
Description:
The kafka-connect fail if the topic can not be join (permission issue or topic doesn't exists).
This issue happend using Debezium CDC : [https://issues.redhat.com/browse/DBZ-1770]
The topic can be choosen using a column on the database. If the topic on a database contains an issue (permission issue or topic doesn't exists), the connect stop to work, and new event will not be sent.
was:
The kafka-connect fail if the topic can not be join (permission issue or topic doesn't exists).
This issue happend using Debezium CDC : [https://issues.redhat.com/browse/DBZ-1770]
The topic can be choosen using a column on the database. If the topic on a database contains an issue (permission issue or topic doesn't exists), the connect stop to work, and new event will not be sent.
> kafka-connect failed when the topic can not be accessed
> -------------------------------------------------------
>
> Key: KAFKA-9522
> URL: https://issues.apache.org/jira/browse/KAFKA-9522
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 2.3.1
> Reporter: Deblock
> Priority: Major
>
> The kafka-connect fail if the topic can not be join (permission issue or topic doesn't exists).
>
> This issue happend using Debezium CDC : [https://issues.redhat.com/browse/DBZ-1770]
>
> The topic can be choosen using a column on the database. If the topic on a database contains an issue (permission issue or topic doesn't exists), the connect stop to work, and new event will not be sent.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)