[
https://issues.apache.org/jira/browse/KAFKA-19086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18009554#comment-18009554
]
Christo Lolov commented on KAFKA-19086:
---------------------------------------
Removing the fix version as it is being picked up by the release tools. Let me
know in case this gets picked up and should be included in 4.0.1!
> 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
> Fix For: 4.0.1
>
>
> 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)
