Skip to content

Tags: andycent/maxwell

Tags

v1.11.0

Toggle v1.11.0's commit message
v1.11.0, "the latest, the greatest"

     - default kafka client upgrades to 0.11.0.1
     - fix the encryption issue (zendesk#803)

v1.10.9

Toggle v1.10.9's commit message

Unverified

This user has not yet uploaded their public signing key.
v1.10.9, "no one left behind"

We recommend all v1.10.7 and v1.10.8 users upgrade to v1.10.9.

 - Add missing Kafka clients
 - Listen and report on binlog connector lifecycle events for better visibility
 - Reduce docker image size

v1.10.8

Toggle v1.10.8's commit message

Unverified

This user has not yet uploaded their public signing key.
v1.10.8, "what doesn't kill you makes you stronger"

 - Fix docker builds
 - Add Google Cloud Pub/Sub producer
 - RabbitMQ producer enhancements

v1.10.7

Toggle v1.10.7's commit message
v1.10.7, "it's never too l8!"

- Java 8 upgrade
- Diagnostic health check endpoint
- Encryption
- Documentation update: encryption, kinesis producer, schema storage fundamentals, etc.

 - list changes

v1.10.6

Toggle v1.10.6's commit message
v1.10.6, "a new starter is here"

 - Binlog-connector upgrade
 - Bug-fix: when using literal string for an option that accepts Regex, Regex characters are no longer special
 - If master recovery is enabled, Maxwell cleans up old positions for the same server and client id

v1.10.5

Toggle v1.10.5's commit message
v1.10.5, "half asleep on her couch"

- Shyko's binlog-connector is now the default and only replication
backend available for maxwell.

v1.10.4

Toggle v1.10.4's commit message
v1.10.4, "shutdown --harder"

Notable changes:

 - Shutdown hardening. If maxwell can't shut down (because the kafka
   producer is in a bad state and `close()` never terminates, for example),
   it would previously stall and process no messages. Now, shutdown is run
   in a separate thread and there is an additional watchdog thread which
   forcibly kills the maxwell process if it can't shut down within 10
   seconds.
 - Initial support for running maxwell from java, rather then as its own
   process. This mode of operation is still experimental, but we'll
   accept PRs to improve it (thanks Geoff Lywood).
 - Fix incorrect handling of negative (pre-epoch dates) when using
   binlog_connector mode (thanks Geoff Lywood).

v1.10.3

Toggle v1.10.3's commit message
v1.10.3, "1.10.2-and-a-bit"

 - tiny release to fix a units error in the `replication.lag` metric
   (subtracting seconds from milliseconds)

v1.10.2

Toggle v1.10.2's commit message
v1.10.2, "just in time for tomorrow"

- added metrics: "replication.queue.time" and "inflightmessages.count"
- renamed "time.overall" metric to "message.publish.time"
- documentation updates (thanks Chintan Tank)

v1.10.1

Toggle v1.10.1's commit message
 v1.10.1, "forgive and forget"

The obserable changes in this minor release are a new configuration for Kafka/Kinesis producer to abort processing on publish errors, and support of Kafka 0.10.2. Also a bunch of good refactoring has been done for heartbeat processing. List of changes:
  - Support Kafka 0.10.2
  - Stop procesing RDS hearbeats
  - Keep maxwell heartbeat going every 10 seconds when database is quiet
  - Allow for empty double-quoted string literals for database schema changes
  - Ignore Kafka/Kinesis producer errors based on new configuration ignore_producer_error