Tags: zhangchao3456/maxwell
Tags
v1.19.0, "whole lotta milka" - mysql 8 support! - utf8 enum values are supported now - fix zendesk#1125, bootstrapping issue for TINYINT(1) - fix zendesk#1145, nasty bug around SQL blacklist and columns starting with "begin" - only resume bootstraps that are targeted at this client_id - fixes for blacklists and heartbeats. Did I ever mention blacklists are a terrible idea?
v1.18.0, "hello from the Andes" - memory optimizations for large schemas (especially shareded schemas with lots of duplicates) - add support for an http endpoint to support Prometheus metrics - allow javascript filters to access the row query object - javascript filters now run in the bootstrap process - support for non-latin1 column names - add `--output_schema_id` option - better handling of packet-too-big errors from Kinesis - add message.publish.age metric
v1.16.0, "kind of sort of a reference to something" v1.16.0 brings a rewrite of Maxwell's filtering system, giving it a concise list of rules that are executed in sequence. It's now possible to exclude tables from a particular database, exclude columns matching a value, and probably some other use cases. See http://maxwells-daemon.io/config/#filtering for details.
v1.15.0, "I'm sure I'm being supportive here." This is a bug-fix release, but it's big enough I'm giving it a minor version. - Fix a very old bug in which DDL rows were writing the *start* of the row into `maxwell.positions`, leading to chaos in some scenarios where maxwell managed to stop on the row and double-process it, as well as to a few well-meaning patches. - Fix the fact that maxwell was outputting "next-position" instead of "position" of a row into JSON. - Fix the master-recovery code to store schema that corresponds to the start of a row, and points the replicator at the next-position. Much thanks to Tim, Likun and others in sorting this mess out.
PreviousNext