Is it possible to trigger Debezium signals simply via sending messages to a preset Kafka topic?

[Brandon Hsu]

Hello, all,

As far as I know, Debezium signaling mechanism works by setting signal table (or signal collection on MongoDB) in source databases.

https://debezium.io/documentation/reference/stable/configuration/signalling.html#debezium-signaling-enabling-signaling

But it is somewhat not convenient if there are many databases set up with Debezium functionality.

I guess that these signal tables/collections are actually sending to the corresponding Kafka topic and monitored by Debezium tasks.

Is it possible to directly sending signal events to these topics?

Or will Debezium support sending signaling directly to specified topics in the future?

Best Regards.

----------------------------------------------------------------------------------------------------------------------------------------------------
本信件(包括任何附件)為機密信件。若您並非指定收信人，嚴禁複製、傳送、公開或使用其所載的全部或部份資料，任何對於本信件未經授權之使用或散播可能帶有法律責任。
若您偶然獲得此郵件，請回信或立即以電話通知寄件人並且從您的電腦系統中刪除本信件及所有附件，謝謝。
The information in this e-mail may be confidential; it is intended for use solely by the individual or entity named as the recipient hereof. Disclosure, copying, distribution, or use of the contents of this e-mail by persons other than the intended recipient may violate applicable laws and if you have received this e-mail in error, please delete the original message and notify us by collect call immediately. Thank you.

----------------------------------------------------------------------------------------------------------------------------------------------------

[Chris Cranford]

Hi Brandon -

So whether we implemented the Kafka topic signal solution for all connectors (currently only MySQL supports it) or you used the database-table approach, there is configuration changes for each connector required.  In addition, each connector would require its own topic.  It isn't just something that gets auto-enabled based on some inspection. 

I think you did raise an interesting point and that is whether we could rely on a single Kafka topic for multiple connector consumers.  This would streamline the configuration for multi-connector deployments on the Kafka side, but unfortunately won't reduce the configuration needed on the per-connector deployment tho.

Thanks,
CC

---------------------------------------------------------------------------------------------------------------------------------------------------- --
You received this message because you are subscribed to the Google Groups "debezium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debezium+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/CA%2BJYH_1pypSoGfhXwK5S5e7ukzduTpN3bVHpNA%2B6TWPMfGC8GQ%40mail.gmail.com.