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-unsubscr...@iceberg.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
