v0.14.2

• capture the mysql database along with the rest of the schema. Eliding it was a bad premature optimization that led to crashes when tables in the mysql database changed.

v0.14.1

• fixes a parser bug around named PRIMARY KEYs.

v0.14.0

This release introduces row filters, allowing you to include or exclude tables from maxwell's output based on names or regular expressions.

v0.13.1

v0.13.1 is a bug fix of v0.13.0 -- fixes a bug where long rows were truncated.

v0.13.0 contains:

• Big performance boost for maxwell: 75% faster in some benchmarks
• @davidsheldon contributed some nice bug fixes around CREATE TABLE ... IF NOT EXISTS, which were previously generating new, bogus copies of the schema.
• we now include a "scavenger thread" that will lazily clean out old, deleted schemas.

v0.13.0

Lucky release number 13 brings some reasonably big changes:

• Big performance boost for maxwell: 75% faster in some benchmarks
• @davidsheldon contributed some nice bug fixes around CREATE TABLE ... IF NOT EXISTS, which were previously generating new, bogus copies of the schema.
• we now include a "scavenger thread" that will lazily clean out old, deleted schemas.

This release has a pretty bad bug. do not use.

v0.12.0

• add support for BIT columns.

v0.11.4

this is another bugfix release that fixes a problem where the replication thread can die in the middle of processing a transaction event. I really need to fix this at a lower level, ie the open-replicator level.

v0.11.3

this is a bugfix release:

• fix problems with table creation options inside alter statements ( ALTER TABLE foo auto_increment=10 )
• fix a host of shutdown-procedure bugs

the test suite should also be way more reliable, not like you care.

v0.11.2

This is a bugfix release. It includes:

• soft deletions of maxwell.schemas to fix A->B->A master swapping without creating intense replication delay
• detect and fail early if we see binlog_row_image=minimal
• kill off maxwell if the position thread dies
• fix a bug where maxwell could pick up a copy of schema from a different server_id (curse you operator precedence!)

v0.11.1

• maxwell gets a very minimal pass at detecting when a master has changed, in which it will kill off schemas and positions from a server_id that no longer is valid. this should prevent the worst of cases.