anchor.diff:  
   === Fixes
   
  +This release includes all of the fixes from the link:release-0-2-1[0.2.1] release plus the following fixes:
  +
   * Correct how the MySQL connector records offsets with multi-row MySQL events so that, even if the connector experiences a non-graceful shutdown (i.e., crash) after committing the offset of _some_ of the rows from such an event, upon restart the connector will resume with the remaining rows in that multi-row event. Previously, the connector might incorrectly restart at the next event. https://issues.jboss.org/projects/DBZ/issues/DBZ-73[DBZ-73]
   * Shutdown of the MySQL connector immediately after a snapshot completes (before another change event is reccorded) will now be properly marked as complete. https://issues.jboss.org/projects/DBZ/issues/DBZ-77[DBZ-77]
   
  -=== Upgrading
  -
  -Upgrading a connector to 0.2.2 from 0.2.1 should be straightforward: gracefully stop the running 0.2.1 connector, remove the 0.2.1 plugin files, install the 0.2.2 plugin files, and restart the connector using the same configuration. Upon restart, the 0.2.2 connector will continue where the previous connector left off. As one might expect, all change events previously written to Kafka by the old connector will not be modified.
  -
   
   [[release-0-2-1]]
   == *Release 0.2.1* _(June 10, 2016)_
   
  -See the https://issues.jboss.org/browse/DBZ/fixforversion/12330752[complete list of issues]
  +See the https://issues.jboss.org/browse/DBZ/fixforversion/12330752[complete list of issues].
   
   === Kafka compatibility
   
   This release can be used with Kafka Connect 0.9.0.1 (or a subsequent API-compatible release), and is known to be _incompatible_ with Kafka Connect 0.10.0 due to https://issues.apache.org/jira/browse/KAFKA-3006[binary incompatible changes in the Kafka 0.10.0 API]. https://issues.jboss.org/projects/DBZ/issues/DBZ-80[DBZ-80]
   
  +=== Upgrading
  +
  +Check the backward-incompatible changes when upgrading to 0.2.1 from 0.2.0.
  +
  +When you decide to upgrading the MySQL connector to 0.2.1 from 0.2.0, gracefully stop the running 0.2.0 connector, remove the 0.2.0 plugin files, install the 0.2.1 plugin files, and restart the connector using the same configuration. Upon restart, the 0.2.1 connector will continue where the previous connector left off. As one might expect, all change events previously written to Kafka by the old connector will not be modified.
  +
   === Backwards-incompatible changes
   
   * Corrected the names of the Avro-compliant Kafka Connect schemas generated by the MySQL connector for the `before` and `after` fields in its data change events. Consumers that require knowledge (by name) of the particular schemas used in 0.2 events may have trouble consuming events produced by the 0.2.1 (or later) connector. https://issues.jboss.org/projects/DBZ/issues/DBZ-72[DBZ-72]
   
   === Fixes
  +
  +This release includes all of the fixes from the link:release-0-2-0[0.2.0] release plus the following fixes:
   
   * The MySQL connector's plugin archive now contains the MySQL JDBC driver JAR file required by the connector. https://issues.jboss.org/projects/DBZ/issues/DBZ-71[DBZ-71]
   
  
positive.code: 
  === Fixes
  
  This release includes all of the fixes from the link:release-0-2-3[0.2.3], link:release-0-2-2[0.2.2], and link:release-0-2-1[0.2.1] releases, and also includes the following fixes:
  
  * Corrected how the MySQL connector handles `TINYINT` columns. https://issues.jboss.org/projects/DBZ/issues/DBZ-84[DBZ-84]
  
  === Upgrading
  
  Upgrading the MySQL connector to 0.3.0 from 0.2.3, 0.2.2, or 0.2.1 should be straightforward: gracefully stop the running connector, remove the old plugin files, install the 0.3.0 plugin files, and restart the connector using the same configuration. Then add the new MongoDB connector plugin files to the classpath, and upon restart, the 0.3.0 MySQL connectors will continue where the previous connector left off. As one might expect, all change events previously written to Kafka by the old connector will not be modified.
  
  
  
  
negative.code: [[release-0-3-0]]
  == *Release 0.3.0* _(July 26, 2016)_
  
  See the https://issues.jboss.org/browse/DBZ/versions/12329661[complete list of issues].
  
  === Kafka compatibility
  
  This release requires Kafka Connect 0.10.0.1 (or a subsequent API-compatible release), and is known to be _incompatible_ with Kafka Connect 0.9.0.x due to https://issues.apache.org/jira/browse/KAFKA-3006[binary incompatible changes in the Kafka 0.10.0 API]. See https://issues.jboss.org/projects/DBZ/issues/DBZ-80[DBZ-80] for details, and Kafka documentation for compatibility with other versions of Kafka brokers.
  
  === Upgrading
  
  Before upgrading the MySQL connector, be sure to check the backward-incompatible changes that have been made since the release you were using.
  
  When you decide to upgrading the MySQL connector to 0.3.0 from 0.2.4, 0.2.3, 0.2.2, or 0.2.1, gracefully stop the running connector, remove the old plugin files, install the 0.3.0 plugin files, and restart the connector using the same configuration. Upon restart, the 0.3.0 MySQL connectors will continue where the previous connector left off. As one might expect, all change events previously written to Kafka by the old connector will not be modified.
  
  === Backwards-incompatible changes
  
  This release includes the potentially backward-incompatible changes from the link:release-0-2-4[0.2.4] release:
  
  * By default the MySQL connector now represents temporal values with millisecond, microsecond, or nanosecond precision based upon the precision of the source database columns. This changes the schema name of these fields to Debezium-specific constants, and the meaning/interpretation of the literal values now depends on this schema name. To enable previous behavior that always used millisecond precision using only Kafka Connect logical types, set `time.precision.mode` connector property to `connect`. https://issues.jboss.org/projects/DBZ/issues/DBZ-91[DBZ-91]
  
  === New Features
  
  