Re: Connector is still in 'RUNNING' status even though the heartbeat failed

I mean " pull request". Ref: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests Thanks. Luke Andreas Gillmann 於 2022年1月31日 週一 下午6:34 寫道： > Hello Luke, > > yes I will do so, but please tell me, what is

Re: Connector is still in 'RUNNING' status even though the heartbeat failed

PR means “Pull Request”. It is a way to have others review your code changes and, when ready, they can merge them in. https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests From: Andreas Gillmann Date:

AW: Connector is still in 'RUNNING' status even though the heartbeat failed

Hello Luke, yes I will do so, but please tell me, what is a PR? Regards, Andreas -Ursprüngliche Nachricht- Von: Luke Chen Gesendet: Sonntag, 30. Januar 2022 10:04 An: Kafka Users Betreff: Re: Connector is still in 'RUNNING' status even though the heartbeat failed Hi Andreas, Could

Re: Connector is still in 'RUNNING' status even though the heartbeat failed

Hi Andreas, Could you open a bug in Kafka JIRA ? And you're welcome to create a PR for this issue. Let me know if you need any help. Thank you. Luke On Wed, Jan 26, 2022 at 9:10 PM Andreas Gillmann <

Connector is still in 'RUNNING' status even though the heartbeat failed

Hello, I have noticed a problem which I have also discussed with RedHat (https://issues.redhat.com/browse/DBZ-4521): Prerequisites: * Debezium connector with heartbeat configuration ( "heartbeat.topics.prefix" is set) * Heartbeat topic on Kafka side does NOT exists * Parameter