This is a small release, primarily around a change to how schemas are
stored. Maxwell now stores the
last_heartbeat_read with each entry
schemas table, making schema management more resilient to
cases where binlog numbers are reused, but means that you must take
care if you need to roll back to an earlier version. If you deploy
v1.10.0, then roll back to an earlier version, you should manually
last_heartbeat_read values to
redeploying v1.10.0 or higher.
Other minor changes:
- allow negative default numbers in columns
- only store final binlog position if it has changed
- blacklist internal aurora table `rds_heartbeat*'
- log4j version bump (allows for one entry per line JSON logging)