Bug #41267 Filtering of replication binlog on master's side.

Submitted: 5 Dec 2008 16:06 Modified: 16 Jan 2009 16:42
Reporter: Piotr Czachur Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Replication Severity:S4 (Feature request)
Version:5.1 OS:Any
Assigned to: Luis Soares CPU Architecture:Any

[5 Dec 2008 16:06] Piotr Czachur
Description:
Now, if I want to replicate just a part of database to untrusted slave I need to create by-pass slave that will filter out binlog entries connected with tables I want to keep secret (using BLACKHOLE engines for this secret tables). I met this limitation many times. 

How to repeat:
--

Suggested fix:
Add options for replication binlog filtering (table level) on master's side, or/and option that enable binlog only for specific tables (currently only database level filtering is supported).
[16 Jan 2009 16:42] Susanne Ebrecht
Many thanks for writing a feature request. This sounds very interested for higher security data. We will discuss this.
[30 Jun 2009 21:56] Luis Soares
Seems that this bug/feature request might be duplicate of BUG#21146.
[26 Mar 2010 12:12] Luis Soares
See also: BUG#2917.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.