anchor.diff:  [[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]. There are no problems upgrading the MySQL connector to 0.3.0 from 0.2.2, 0.2.1, or 0.2.0.
  -
  -=== Kafka compatibility
  -
  -This release requires Kafka Connect 0.10.0.0 (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.
  -
  -=== Backwards-incompatible changes
  -
  -There are no changes to behavior or public APIs compared to the link:#release-0-2-3[0.2.2 release].
  +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
   
  
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-2-3]]
  == *Release 0.2.3* _(July 26, 2016)_
  
  See the https://issues.jboss.org/browse/DBZ/versions/12330932[complete list of issues].
  
  === Kafka compatibility
  
  This release requires 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]. See https://issues.jboss.org/projects/DBZ/issues/DBZ-80[DBZ-80] for details.
  
  === Upgrading
  
  There are no backward-incompatible changes when upgrading to 0.2.3 from 0.2.2. Gracefully stop the running 0.2.2 connector, remove the 0.2.2 plugin files, install the 0.2.3 plugin files, and restart the connector using the same configuration. Upon restart, the 0.2.3 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.
  
  
  === Fixes
  
  This release includes all of the fixes from the link:release-0-2-2[0.2.2] release plus the following fixes:
  
  * Corrected parsing errors when MySQL DDL statements are generated by Liquibase. https://issues.jboss.org/projects/DBZ/issues/DBZ-83[DBZ-83]
  * Corrected support of MySQL `TINYINT` and `SMALLINT` types. https://issues.jboss.org/projects/DBZ/issues/DBZ-84[DBZ-84], https://issues.jboss.org/projects/DBZ/issues/DBZ-87[DBZ-87]
  * Corrected support of MySQL temporal types, including `DATE`, `TIME`, and `TIMESTAMP`. https://issues.jboss.org/projects/DBZ/issues/DBZ-85[DBZ-85]
  * Corrected call to MySQL SHOW MASTER STATUS so that it works on pre-5.7 versions of MySQL. https://issues.jboss.org/projects/DBZ/issues/DBZ-82[DBZ-82]
  
  [[release-0-2-2]]
  == *Release 0.2.2* _(June 22, 2016)_
  
  See the https://issues.jboss.org/browse/DBZ/versions/12330862[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]. See https://issues.jboss.org/projects/DBZ/issues/DBZ-80[DBZ-80] for details.
  
  === Upgrading
  
  Check the backward-incompatible changes when upgrading to 0.2.2 from 0.2.1 or 0.2.0.
  
  When you decide to upgrading the MySQL connector to 0.2.2 from 0.2.1 or 0.2.0, 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.
  
  
  === Backwards-incompatible changes
  
  