rusuly / mysql_cdc Goto Github PK

• BinlogClient
• Row events
• GTID
• Write tests
• Write docs
• Replace panic!, unwrap and expect with Result
• Implement SSL
• Add buffering(like PipeReader from C#)
• Handle split packets
• Parse MySQL JSON
• Handle heartbeat timeout and cancellation

Thanks for supporting the additional binlog event, but release 0.1.7 was backward incompatible.

Please consider yanking the release 0.1.7 and re-release it as version 0.2.0. Thanks!

Reference:

• d03109b

There appears to be a case where a freshly started MySQL server is accepting a connection from mysql_cdc, but ignoring the request to start sending replication events.

Instead, a call to replicate() just blocks, even if blocking is disabled, because it never receives any data.

If the server is just swallowing the request to start, is it possible to instead wait for the FORMAT_DESCRIPTION_EVENT event and, on a timeout, raise an error or potentially attempt to connect again?

At the moment our workaround is to attempt to connect to the server using connect() and, when connected, to wait 10 seconds before attempting to start calling replicate() however, this is both slow in the normal case and potentially still prone to errors if 10 seconds isn't enough for the server to actually be ready to accept new replicas.

Is there a good way to filter table names? such as the canal do.