suxiaogang223 commented on issue #12370:
URL: https://github.com/apache/hudi/issues/12370#issuecomment-2516106669
> Hi @suxiaogang223
>
> Thanks for reporting this issue. I am able to reproduce it. Please allow
some time to provide a solution.
>
> Mean while could you please check what is the timezone where you are
running hive shell from the terminal?
>
> ```shell
> timedatectl
> ```
>
> When i check the parquet file data it is having in micro seconds format.
>
> ```shell
> _hoodie_commit_time: string
> _hoodie_commit_seqno: string
> _hoodie_record_key: string
> _hoodie_partition_path: string
> _hoodie_file_name: string
> id: int32
> time: timestamp[us, tz=UTC]
> ----
> _hoodie_commit_time: [["20241202103846073"]]
> _hoodie_commit_seqno: [["20241202103846073_0_0"]]
> _hoodie_record_key: [["20241202103846073_0_0"]]
> _hoodie_partition_path: [[""]]
> _hoodie_file_name:
[["730743c3-73b3-473b-82f8-fa242d7e78b4-0_0-13-56_20241202103846073.parquet"]]
> id: [[1]]
> time: [[2024-11-28 12:00:00.123456Z]]
> ```
>
> This inconsistency is happened due to hive query engine.
Thanks for replay
The result is
```
timedatectl
Local time: Wed 2024-12-04 11:40:17 CST
Universal time: Wed 2024-12-04 03:40:17 UTC
RTC time: Wed 2024-12-04 03:40:16
Time zone: Asia/Shanghai (CST, +0800)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
```
The difference in time is expected behavior, because spark does not parse
timestamp according to UTC format, mainly the difference between precision, is
there a way to make hive output accurate to microseconds?
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
