> This will work but you need to duplicate the mysql.ddl and therefore maintain it on your own, even if there is a small chance it will change over time because it will imply a migration process.
OTOH, IIUC with the proposed patch it's not possible anymore to implicitly use the default engine, e.g. overriden in my.cnf.
> Another thing is that the default table engine is often MyISAM and this engine is not supported in a cluster config.
> Indeed, there will be no RDBMS locking involved when accessing the journal table and data integrity will not be enforced.
in which case you'd have to specify a different engine in my.cnf.