This worklog has been replaced with mariadb.org/jira

This site is here for historical purposes only. Do not add or edit tasks here!

 
 
 

WorkLog Frontpage Log in / Register
High-Level Description | Task Dependencies | High-Level Specification | Low-Level Design | File Attachments | User Comments | Time Estimates | Funding and Votes | Progress Reports

 Make --replicate-(do,ignore)-(db,table) behaviour for RBR identical to that of SBR
Title
Task ID49
Queue
Version N/A
Status
PriorityN/A
Copies to
Created byPsergey16 Aug 2009Done
Supervisor N/A  
Lead Architect    
Architecture Review  
Implementor  
Code Review  
QA  
Documentation  
 High-Level 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.


 Task Dependencies
Others waiting for Task 49Task 49 is waiting forGraph
 
 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
 Low-Level Design
 File Attachments
 NameTypeSizeByDate
 User Comments
 Time Estimates
NameHours WorkedLast Updated
Total0 
 Hrs WorkedProgressCurrentOriginal
Total000
 
 Funding and Votes
Votes: 1: 0%
 Change vote: Useless    Nice to have    Important    Very important    

Funding: 0 offers, total 0 Euro
 Progress Reports
(Guest - Thu, 17 Jun 2010, 00:38
    
Dependency deleted: WL#39 no longer depends on WL#49

(Psergey - Sun, 16 Aug 2009, 12:07
    
Dependency created: WL#39 now depends on WL#49

(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.
 
 
 


Report Generator:
 
Saved Reports:

WorkLog v4.0.0
  © 2010  Sergei Golubchik and Monty Program AB
  © 2004  Andrew Sweger <yDNA@perlocity.org> and Addnorya
  © 2003  Matt Wagner <matt@mysql.com> and MySQL AB