You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by "akomisarek (via GitHub)" <gi...@apache.org> on 2025/08/20 16:36:39 UTC

[I] What is design decision / rationale behind treating Kafka Connect timestamp as timezone aware [iceberg]

akomisarek opened a new issue, #13876:
URL: https://github.com/apache/iceberg/issues/13876

   ### Query engine
   
   N/A - not/relevant as the question is about writing/creating tables via Iceberg KafkaConnect
   
   ### Question
   
   As per KafkaConnect API https://kafka.apache.org/40/javadoc/org/apache/kafka/connect/data/Timestamp.html Timestamp is wallclock - timestamp representing absolute time without timezone information. 
   
   However, when autocreating Iceberg tables/converting KafkaConnect schema to Iceberg types, the timezone aware type is used via https://github.com/apache/iceberg/blob/07c088fce9c54369864dcb6da16006e78206048b/kafka-connect/kafka-connect/src/main/java/org/apache/iceberg/connect/data/SchemaUtils.java#L250-L253. 
   
    The above creates table with `timestamp with timezone` type instead of (maybe?) expected `timestamp without timezone` (I assume that's the reason, couldn't find the appropriate code)
   
   I am trying to figure out how to best to handle timezones when using autocreation and KafkaConnect, and this behaviour took me by surprise. 
   
   Ideally, persistent timezone would be great, but there is no way to truly pass it from Kafka Connect, so why this discrepancy? I am for sure missing something as working with timezones is hard!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [I] What is design decision / rationale behind treating Kafka Connect timestamp as timezone aware [iceberg]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #13876:
URL: https://github.com/apache/iceberg/issues/13876#issuecomment-4365048419

   This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale'


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [I] What is design decision / rationale behind treating Kafka Connect timestamp as timezone aware [iceberg]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #13876: What is design decision / rationale behind treating Kafka Connect timestamp as timezone aware
URL: https://github.com/apache/iceberg/issues/13876


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [I] What is design decision / rationale behind treating Kafka Connect timestamp as timezone aware [iceberg]

Posted by "rockwotj (via GitHub)" <gi...@apache.org>.
rockwotj commented on issue #13876:
URL: https://github.com/apache/iceberg/issues/13876#issuecomment-3422824651

   Because it's explicitly in kafka `System.currentTimeMillis()`: https://docs.oracle.com/javase/8/docs/api/java/lang/System.html#currentTimeMillis--
   
   Which is defined as milliseconds since the unix Epoch UTC.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [I] What is design decision / rationale behind treating Kafka Connect timestamp as timezone aware [iceberg]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #13876:
URL: https://github.com/apache/iceberg/issues/13876#issuecomment-4274855846

   This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org