You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Pritam Kumar (Jira)" <ji...@apache.org> on 2026/04/07 10:05:00 UTC

[jira] [Updated] (KAFKA-19086) Extending support for Microsecond Precision for Kafka Connect

     [ https://issues.apache.org/jira/browse/KAFKA-19086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pritam Kumar updated KAFKA-19086:
---------------------------------
    Reviewer: Pritam Kumar

> Extending support for Microsecond Precision for Kafka Connect
> -------------------------------------------------------------
>
>                 Key: KAFKA-19086
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19086
>             Project: Kafka
>          Issue Type: Improvement
>          Components: connect
>            Reporter: Pritam Kumar
>            Priority: Major
>
> While formats like {*}Avro{*}, {*}Parquet{*}, and others support higher precision timestamps (including microseconds :: [https://avro.apache.org/docs/1.11.0/spec.html|https://avro.apache.org/docs/1.11.0/spec.html#Timestamp+%28microsecond+precision%29]), Kafka Connect has been limited to handling only millisecond precision (timestamp). 
> As a result, any timestamp data expressed in microseconds is truncated when communicated between the Kafka Connect source and sink, leading to potential loss of precision and data fidelity.
> This change aims to extend the logical timestamp support in Kafka Connect to include timestamp-micros. By doing so, it ensures that the full precision of time data can be communicated accurately across the entire pipeline without any loss of information.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)