Bug #61465 RFE: binlog-ignore-engine=...
Submitted: 9 Jun 2011 20:31 Modified: 10 Jul 2011 4:27
Reporter: Kevin Benton Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:5.1.47 OS:Any
Assigned to: CPU Architecture:Any

[9 Jun 2011 20:31] Kevin Benton 
Description:
Please add the ability to skip storage engines for the purpose of binary logging. Most of the data we need point-in-time recovery on is stored in either InnoDB or NDBCluster. What I don't want to do is to fill up binary logs with data from storage engines like FEDERATED, MyISAM, ARCHIVE, ...

There are also times when I want to replicate data that's kept on SQL nodes that are cluster participants but that data is not kept in the NDBCluster storage engine.

Sorry if this is a dupe RFE. I didn't see request anywhere else.

How to repeat:
See description.

Suggested fix:
See description.
[10 Jun 2011 4:27] Valeriy Kravchuk 
What if several tables are changed in one statement, some of them InnoDB ones and others MyISAM? Should the entire statement be ignored? What if it's a part of transaction?
[10 Jul 2011 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".