You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "Abacn (via GitHub)" <gi...@apache.org> on 2023/05/31 19:33:17 UTC

[GitHub] [beam] Abacn commented on issue #26942: [Bug]: Timestamp off by timezone offset when using Python BigQuery Avro File load

Abacn commented on issue #26942:
URL: https://github.com/apache/beam/issues/26942#issuecomment-1570823454

   > Is all we need here to configure fastavro differently
   
   There is different ways to resolve it. The underlying issue is more subtle (see below) and there are many ways to resolve the issues.
   
   Another way is to add time zone info in 
   
   https://github.com/apache/beam/blob/bdd29bf45f818ce0c20c111c9787d5051c1b792b/sdks/python/apache_beam/utils/timestamp.py#L163
   
   I am not sure why it intentionally removed tzinfo at first place. A datetime.datetime object without a time zone implicitly means local time zone (as the object returned by datetime.datetime.now()) so the current returned object is not correct in my view.
   
   > would this apply to any avro usage?
   
   Only apply to write a datetime object returned from apache_beam.utils.timestamp.Timestamp.to_utc_datetime
   
   
   


-- 
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: github-unsubscribe@beam.apache.org

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