You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Daniel Petisme (Jira)" <ji...@apache.org> on 2020/09/30 21:30:00 UTC

[jira] [Created] (KAFKA-10561) Support microseconds precision for Timestamps

Daniel Petisme created KAFKA-10561:
--------------------------------------

             Summary: Support microseconds precision for Timestamps
                 Key: KAFKA-10561
                 URL: https://issues.apache.org/jira/browse/KAFKA-10561
             Project: Kafka
          Issue Type: Improvement
          Components: KafkaConnect
            Reporter: Daniel Petisme


Kafka connect model 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 the conversion to java.utilDate is wrong.

I can't check myself but I heard that IBM CDC was also using `timestamp-micros`.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)