Add binlog replication example #247
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for MySQL binlog replication.
Changes:
trilogy_binlog_dump()andtrilogy_binlog_dump_recv()functionsexample/trilogy_binlog) demonstrating binlog replicationFORMAT_DESCRIPTION_EVENT,TABLE_MAP_EVENT, andWRITE_ROWS_EVENTSIGINThandler for graceful shutdownThe example connects to a MySQL server and streams binlog events, printing row data as they are received.
Testing Note
This change introduces
COM_BINLOG_DUMPsupport and requires a MySQL server with replication enabled (--log-bin,--server-id, etc.) for end-to-end validation.Since Trilogy's current test suite does not spin up such an environment, unit-level tests are omitted.
The implementation has been verified in production systems for over a year without issues.