Need a way to permanently filter certain schemas from the replication stream

Bug #716502 reported by David Shrewsbury
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
High
Brian Aker
7.0
Fix Released
High
Brian Aker

Bug Description

We need a way, other than using filtered_replicator plugin, to permanently block actions on certain schema from going through the replication stream. For instance, work being done for bug 711068 requires us to block modifications on a new table in D_D linking to the innodb transaction log.

This is also needed for this blueprint: https://blueprints.launchpad.net/drizzle/+spec/replication-native

The slave plugin stores its state information in it's own schema and tables, and these should never be replicated.

Tags: replication

Related branches

Revision history for this message
David Shrewsbury (dshrews) wrote :

Assigning to Brian. He has a better solution.

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

Is this ready to close after my branch is merged? Or is there something else we need to do too?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.