Error 'Table .. does not exist' suggests that you are trying a slightly different scenario comparing to the one you described in the original bug. There was no CREATE TABLE hidden from slave, only DML (DELETE).
I am trying the scenario that you and Sveta described in the MySQL bug, and it works all right for me, both on MariaDB 5.2.10 and MySQL 5.1.60. However, a slightly different one, which involves DDL, fails, also both on MariaDB and MySQL, with the exact error that you mentioned. Something like this:
SET binlog_format='row';
SET SQL_LOG_BIN=0;
CREATE TABLE t ( i INT );
INSERT INTO t VALUES (1);
SET SQL_LOG_BIN=1;
DELETE FROM t;
# check slave status, observe error 1146 and slave SQL thread not running.
Could you please confirm that's what you encountered?
I suppose this flow has never been fixed, or possibly was broken again. I It fails on MySQL 5.1.60 and 5.1.57, but I don't have older versions to check.
Error 'Table .. does not exist' suggests that you are trying a slightly different scenario comparing to the one you described in the original bug. There was no CREATE TABLE hidden from slave, only DML (DELETE).
I am trying the scenario that you and Sveta described in the MySQL bug, and it works all right for me, both on MariaDB 5.2.10 and MySQL 5.1.60. However, a slightly different one, which involves DDL, fails, also both on MariaDB and MySQL, with the exact error that you mentioned. Something like this:
SET binlog_ format= 'row';
SET SQL_LOG_BIN=0;
CREATE TABLE t ( i INT );
INSERT INTO t VALUES (1);
SET SQL_LOG_BIN=1;
DELETE FROM t;
# check slave status, observe error 1146 and slave SQL thread not running.
Could you please confirm that's what you encountered?
I suppose this flow has never been fixed, or possibly was broken again. I It fails on MySQL 5.1.60 and 5.1.57, but I don't have older versions to check.