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

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

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

    [ https://issues.apache.org/jira/browse/KAFKA-10561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205039#comment-17205039 ] 

Daniel Petisme commented on KAFKA-10561:
----------------------------------------

I would be more than happy to propose a PR if  I can get some guidance.

> 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
>            Priority: Minor
>
> 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`.



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