PXC triggers that modify MyISAM tables not working

[Brian Fraser]

To replicate:
1) Load some nodes with wsrep-replicate-myisam.
2) Load sakila-db (or the attached test case) on one node
3) Check that sakila.film_text has data on that node

At this point, film_text will be empty on the other nodes, and their error logs will have entries like

121008 17:13:41 [ERROR] Slave SQL: Error 'Unknown column 'new.film_id' in 'field list'' on query. Default database: 'sakila'. Query: 'INSERT INTO film_text (film_id, title, description)
        VALUES (new.film_id, new.title, new.description)', Error_code: 1054
121008 17:13:41 [Warning] WSREP: RBR event 1 Query apply warning: 1, 35
121008 17:13:41 [Warning] WSREP: Ignoring error for TO isolated action: source: 91dec4df-1184-11e2-0800-004c682044c6 version: 2 local: 0 state: APPLYING flags: 65 conn_id: 7 trx_id: -1 seqnos (l: 39, g: 35, s: 34, d: 34, ts: 1349727221123515580)

[Daniel Nichter (daniel-nichter)]

We've had about 8 months of experience with PXC now, and the verdict seems clear: PXC and MyISAM are not a good combination, and afaik there's no big push from users to make it work, i.e. the 99% use-case is PXC with InnoDB. So I'm going to WontFix this bug in Percona Toolkit.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1035