anchor.diff:  |`TIME`, `TIME(0)`, `TIME(1)`, `TIME(2)`, `TIME(3)` 
   |`INT32`
   |`io.debezium.time.Time`
  -| Represents the number of milliseconds past midnight.
  +| Represents the number of milliseconds past midnight, and does not include timezone information.
   
   |`TIME(4)`, `TIME(5)`, `TIME(6)` 
   |`INT64`
   |`io.debezium.time.MicroTime`
  -| Represents the number of microseconds past midnight.
  +| Represents the number of microseconds past midnight, and does not include timezone information.
   
   |`DATETIME`, `DATETIME(0)`, `DATETIME(1)`, `DATETIME(2)`, `DATETIME(3)` 
   |`INT64`
   |`io.debezium.time.Timestamp`
  -| Represents the number of milliseconds past epoch.
  +| Represents the number of milliseconds past epoch, and does not include timezone information.
   
   |`DATETIME(4)`, `DATETIME(5)`, `DATETIME(6)`
   |`INT64`
   |`io.debezium.time.MicroTimestamp`
  -| Represents the number of microseconds past epoch.
  +| Represents the number of microseconds past epoch, and does not include timezone information.
   
   |=======================
   
  
positive.code: |`TIME[(M)]` 
  |`INT64`
  |`org.apache.kafka.connect.data.Time`
  | Represents the number of milliseconds since midnight.
  
  |`DATETIME[(M)]` 
  |`INT64`
  |`org.apache.kafka.connect.data.Timestamp`
  | Represents the number of milliseconds since epoch.
  
  |=======================
  
  However, when `time.precision.mode` configuration property is set to `adaptive`, then the connector will base the literal type and semantic type for the temporal types on the column's data type definition:
  
  [cols="15%a,15%a,35%a,35%a",width=100,options="header,footer",role="table table-bordered table-striped"]
  |=======================
  
negative.code: |`TIMSTAMP[(M)]`
  |`STRING`
  |`io.debezium.time.ZonedTimestamp`
  | Contains an ISO8601 formatted date and time (with up to microsecond precision) in a particular time zone. MySQL allows `M` to be in the range 0-6 to store up to microsecond precision.
  
  |=======================
  
  