You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by GitBox <gi...@apache.org> on 2021/11/11 03:12:51 UTC

[GitHub] [hudi] Frogglet edited a comment on issue #3965: [SUPPORT] Upserts result in truncated milliseconds from timestamps

Frogglet edited a comment on issue #3965:
URL: https://github.com/apache/hudi/issues/3965#issuecomment-965950614


   @xushiyan Hey, I'm using AWS Glue for my Hive metastore, and according to glue the type for these timestamps is just "bigint". So, it's not changing the schema, it is just integer dividing by 1000. For example, before this change, a value might be `1628643404092`, which is a unix timestamp in milliseconds. After my upsert, if that row was affected the value would become `1628643404`, losing the millisecond information.
   
   One source for these timestamps for me is just calling the sparksql builtin `current_timestamp()`. Also I should have mentioned I have hive syncing turned on.


-- 
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: commits-unsubscribe@hudi.apache.org

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