LsomeYeah opened a new issue, #5722: URL: https://github.com/apache/paimon/issues/5722
### Search before asking - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. ### Paimon version Paimon's version: 1.2-snapshot(2025/06/09) ### Compute Engine Hive's version: hive 2.3.10 Flink's version: 1.20.1 ### Minimal reproduce step When selecting the paimon table which was cloned from hive through hive-clone action, the selected result for timestamp is different between paimon and hive. **Note: file format is parquet.** Minimal reproduce step: 1. create a table in hive and insert some data: ```sql -- create a table CREATE TABLE test.hive_test_table( `a` int COMMENT 'The a field', `ts` timestamp COMMENT 'The ts field' ) STORED AS PARQUET; -- insert a value INSERT INTO test.hive_test_table VALUES (1, '2025-06-03 16:00:00'); -- select SELECT * FROM test.hive_test_table; -- result: 1, 2025-06-03T16:00 ``` 2. run hive-clone action 3. select the cloned paimon table in flink ```sql SELECT * FROM paimon_hive_test_table; -- result: 1, 2025-06-03T08:00 ``` The reaseon may be: Hive will transform the timestamp to UTC for storage, and transform the stored timestamp to `writer.time.zone` or system default time zone when reading. While paimon will directly read the original timestamp stored in parquet file without any transforms, this leads to difference. ### What doesn't meet your expectations? The selected result for timestamp has changed after cloning to paimon. ### Anything else? _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- 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...@paimon.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
