Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Kafka connect Timestamp logical type has a milliseconds precision where AVRO provide both milli and micro seconds precision (for both Time and Timestamp).
I faced the issue when using Qlik Replicate (former Attunity) Change Data Capture (CDC)tool. The CDC serializes timestamp with a microseconds precision and provide the official `timestamp-micros` logical type.
Due to the lack of support, SMTs like TimestampConverter fallback to a Long representation (since internally the `timestamp-micros` does not exists) and then conversion to java.utilDate is wrong since it expects the Long to represent millis and not micro seconds.
I can't check myself but I heard that IBM CDC was also using `timestamp-micros`.