the last sql don't commit with dropcomments and dropstatementdata

[GoogleCodeExporter]

What steps will reproduce the problem?
mysql->postgresql 2.1.1
1.with replicator.stage.q-to-dbms.filters=dropcomments,dropstatementdata
2.in master(mysql):mysqldump test table1 >table1.dump
3.in master(mysql):mysql test <table1.dump
4.in slave(postgresql):select * from table1;
What is the expected output?
I want to testing for mysql restore with dumpfile,
and use 'dropcomments,dropstatementdata' option to filter the command that like 
:/*!40000 ALTER TABLE `kuyun_system_user` ENABLE KEYS */;
...
What do you see instead?
but in postgresql(slave): the command don't commit until execute other command 
in mysql .
...

What version of the product are you using?

...

On what operating system?
master:Tungsten Replicator 2.1.2 build 30
slave:Tungsten Replicator 2.1.1 build 191
...

Please provide any additional information below.

Notes:

...

Original issue reported on code.google.com by dppassdf...@gmail.com on 12 Oct 2013 at 9:35

[GoogleCodeExporter]

Which Replicator build are you running? We fixed some issues with filters and 
commits long time ago.

How did you install this topology? You might have something mixed up in the 
queues.

Original comment by linas.vi...@continuent.com on 14 Oct 2013 at 9:48

[GoogleCodeExporter]

Original comment by linas.vi...@continuent.com on 14 Oct 2013 at 9:49

• Added labels: PostgreSQL

[GoogleCodeExporter]

I use the replication is 2.1.1 build 191

the master is mysql,the slave is postgresql

the  static-t_to_stat.properties file like config.txt

Original comment by dppassdf...@gmail.com on 15 Oct 2013 at 2:14

Attachments:

• config.txt

[GoogleCodeExporter]

2.1.1 release has been dismissed due to a critical bug. Instead of mixing 
different Replicator versions, try upgrading your slave to 2.1.2-30 first.

Original comment by linas.vi...@continuent.com on 15 Oct 2013 at 6:08