TenDB have enhanced mysqlbinlog to filter binlog row_events.
It's useful to track the change of some record, and no need to scrape the rows from massive output of mysqlbinlog. Just use --filter-rows options to filter rows out, and its result can be applied to mysqld.
Work with --flashback options, the binlog_event is reverted. That's:
- WRITE_ROWS_EVENT is converted to DELETE_ROWS_EVENT
- DELETE_ROWS_EVENT is converted to WRITE_ROWS_EVENT
- Exchange the before and after image for UPDATE_ROWS_EVENT
This feature need binlog_format=ROW and binlog_row_image=FULL. You can use --query-event-handler and --filter-statement-match-[handler] to tell mysqlbinlog how to handle QUERY_EVENT.
Combine this options together, mysqlbinlog flashback support specific records rollback in a short time.
Read this docs to get more info: https://tendbcluster.com/book-cn/Documentation/tendb/mysqlbinlog-flashback.html
TenDB have enhanced mysqlbinlog to filter binlog row_events.
It's useful to track the change of some record, and no need to scrape the rows from massive output of mysqlbinlog. Just use
--filter-rowsoptions to filter rows out, and its result can be applied to mysqld.Work with
--flashbackoptions, the binlog_event is reverted. That's:This feature need
binlog_format=ROWandbinlog_row_image=FULL. You can use--query-event-handlerand--filter-statement-match-[handler]to tell mysqlbinlog how to handle QUERY_EVENT.Combine this options together, mysqlbinlog flashback support specific records rollback in a short time.
Read this docs to get more info: https://tendbcluster.com/book-cn/Documentation/tendb/mysqlbinlog-flashback.html