Closed jpeyper closed 8 years ago
huh. what version of mysql? I can certainly add this to the blacklist as Maxwell doesn't care about temporary tables, but according to https://dev.mysql.com/doc/refman/5.6/en/replication-features-temptables.html this isn't supposed to happen with row-based replication.
SELECT VERSION()
tells me 5.6.25-enterprise-commercial-advanced-log
I also got this error today. removed private data from query
12:45:12,219 ERROR SchemaChange - Error parsing SQL: 'CREATE OR REPLACE xyz=UNDEFINED DEFINER=`xyz`@`%` SQL zyz VIEW `zyz` AS SELECT a.ztzAS xyz, a.zyzAS zyx, a.xyzAS xyz, a.xyzAS xyz, b.xyzAS xyz, b.xyzAS xyz, b.xyzAS xyz, b.xyzAS blab , FROM xyz AS a, xyx AS b WHERE a.xyz= b.xyz'
com.zendesk.maxwell.schema.ddl.MaxwellSQLSyntaxError: CREATE
at com.zendesk.maxwell.schema.ddl.MysqlParserListener.visitErrorNode(MysqlParserListener.java:85)
at org.antlr.v4.runtime.tree.ParseTreeWalker.walk(ParseTreeWalker.java:41)
at org.antlr.v4.runtime.tree.ParseTreeWalker.walk(ParseTreeWalker.java:52)
at org.antlr.v4.runtime.tree.ParseTreeWalker.walk(ParseTreeWalker.java:52)
at com.zendesk.maxwell.schema.ddl.SchemaChange.parse(SchemaChange.java:67)
at com.zendesk.maxwell.MaxwellReplicator.processQueryEvent(MaxwellReplicator.java:274)
at com.zendesk.maxwell.MaxwellReplicator.getRow(MaxwellReplicator.java:254)
at com.zendesk.maxwell.MaxwellReplicator.work(MaxwellReplicator.java:87)
at com.zendesk.maxwell.RunLoopProcess.runLoop(RunLoopProcess.java:31)
at com.zendesk.maxwell.Maxwell.run(Maxwell.java:89)
at com.zendesk.maxwell.Maxwell.main(Maxwell.java:95)
12:45:12,220 INFO SchemaPosition - Storing final position: BinlogPosition[binarylog.023492:6773]
@xmlking, I opened https://github.com/zendesk/maxwell/pull/185/files the other day for view creation. @jpeyper has got himself a very odd config in which he's getting some row-based and some statement-based stuff.
Also, I'm doing what I've needed to do for awhile which is run maxwell against the mysql test suite and fix a bunch of the lingering parse problems.
Thanks @osheroff . Appreciate your work and support.
both issues fixed in v0.16.1
I had this error occur today.