maria-developers team mailing list archive

[worklog-noreply@xxxxxxxxxxxx]

-----------------------------------------------------------------------
                              WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...........: @@binlog_do_not_replicate filtering of binlog events
CREATION DATE..: Mon, 01 Aug 2011, 09:40
SUPERVISOR.....: Monty
IMPLEMENTOR....: Knielsen
COPIES TO......: 
CATEGORY.......: Server-Sprint
TASK ID........: 234 (http://askmonty.org/worklog/?tid=234)
VERSION........: Server-9.x
STATUS.........: Assigned
PRIORITY.......: 60
WORKED HOURS...: 0
ESTIMATE.......: 0 (hours remain)
ORIG. ESTIMATE.: 0

PROGRESS NOTES:



DESCRIPTION:

This worklog is about introducing a new session variable
@@binlog_do_not_replicate.

When this variable is set, an associated flag bit is set in events logged into
the binlog.

The first stage of this worklog is to introduce an option
--slave-ignore-do-not-replicate-events. When this is set, the slave will skip
any events received with the binlog-do-not-replicate bit set.

The second stage is to do this filtering on the master. When
--slave-ignore-do-not-replicate-events is set on the slave, the master will
avoid sending these events to that slave at all, saving on bandwidth but
otherwise working the same way as stage 1.

The motivation for this worklog is to allow an application to do changes that
are replicated in a way external to the internal MySQL replication, but which
still keeps the events in the binlog for debugging/point-in-time recovery, or
for standard replication to other servers.


ESTIMATED WORK TIME

ESTIMATED COMPLETION DATE
-----------------------------------------------------------------------
WorkLog (v4.0.0)