Re: [I] [Spark, PyIceberg] Different behavior in downcasting ns [iceberg]

["JeonDaehong (via GitHub)" <gi...@apache.org>]

JeonDaehong commented on issue #13679:
URL: https://github.com/apache/iceberg/issues/13679#issuecomment-3166132355

   Hi, I'm seeing issues when reading Parquet files with timestamp[ns]. PyIceberg downcasts to us, but Spark misinterprets the values and shows timestamps far in the future.
   
   Is there a recommended way to handle timestamp[ns] with Iceberg? Would normalizing to us before writing be the best option, or is there a better approach?
   
   Thanks!


-- 
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