← Back to team overview

maria-developers team mailing list archive

Updated (by Psergey): Make --replicate-(do, ignore)-(db, table) behaviour for RBR identical to that of SBR (49)

 

-----------------------------------------------------------------------
                              WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...........: Make --replicate-(do,ignore)-(db,table) behaviour for RBR identical to
		that of SBR
CREATION DATE..: Sun, 16 Aug 2009, 12:01
SUPERVISOR.....: Monty
IMPLEMENTOR....: 
COPIES TO......: 
CATEGORY.......: Server-RawIdeaBin
TASK ID........: 49 (http://askmonty.org/worklog/?tid=49)
VERSION........: Server-9.x
STATUS.........: Un-Assigned
PRIORITY.......: 60
WORKED HOURS...: 0
ESTIMATE.......: 0 (hours remain)
ORIG. ESTIMATE.: 0

PROGRESS NOTES:

-=-=(Psergey - Sun, 16 Aug 2009, 12:06)=-=-
High-Level Specification modified.
--- /tmp/wklog.49.old.14928     2009-08-16 12:06:27.000000000 +0300
+++ /tmp/wklog.49.new.14928     2009-08-16 12:06:27.000000000 +0300
@@ -1 +1,12 @@
+Some notes:
+
+The only required changes are on the slave. The slave can see bounds between
+statements (they are delimited by Query_event and Table_map_event entries),
+Table_map_event lists all tables that are going to be updated => it is possible
+to make a decision whether we should skip the statement, and if yes, skip all
+RBR events that belong to the statement. 
+
+Possible syntax for options
+--replicate-wild-ignore-stmt-with-table=%.tmptbl%
+--replicate-ignore-stmt-with-table=tmptbl
 

-=-=(Psergey - Sun, 16 Aug 2009, 12:02)=-=-
High Level Description modified.
--- /tmp/wklog.49.old.14739     2009-08-16 12:02:05.000000000 +0300
+++ /tmp/wklog.49.new.14739     2009-08-16 12:02:05.000000000 +0300
@@ -6,8 +6,8 @@
 This can be inconvenient, and also the semantics gets really complicated when
 --binlog_format=mixed is used.
 
-This WL entry is about making processing of RBR events to work the same as SBR
-events did.
+This WL entry is about adding an option to make processing of RBR events to work
+the same as SBR events did.
 
 
 



DESCRIPTION:

At the moment semantics of --replicate-(do,ignore)-(db,table) rules is
different for RBR and SBR:

http://dev.mysql.com/doc/refman/5.1/en/replication-rules-table-options.html

This can be inconvenient, and also the semantics gets really complicated when
--binlog_format=mixed is used.

This WL entry is about adding an option to make processing of RBR events to work
the same as SBR events did.




HIGH-LEVEL SPECIFICATION:



Some notes:

The only required changes are on the slave. The slave can see bounds between
statements (they are delimited by Query_event and Table_map_event entries),
Table_map_event lists all tables that are going to be updated => it is possible
to make a decision whether we should skip the statement, and if yes, skip all
RBR events that belong to the statement. 

Possible syntax for options
--replicate-wild-ignore-stmt-with-table=%.tmptbl%
--replicate-ignore-stmt-with-table=tmptbl


ESTIMATED WORK TIME

ESTIMATED COMPLETION DATE
-----------------------------------------------------------------------
WorkLog (v3.5.9)