bigquery: Timestamps no longer returned in UTC by default #9407
Labels
api: bigquery
Issues related to the BigQuery API.
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Hi!
Breaking change in v1.59.0 not listed as breaking/intentional.
I'm not sure if this was intentional or if you follow semver for >= v1.0.0 but after bumping a minor version of
bigquery
our code stopped working as expected because the client no longer returns data the same way. This change is not noted as breaking in the release log.With the code noted belove, this is my result:
I'm aware of the
DATETIME
function that allows me to specify timezone, however not all queries is easy enough to manipulate by replacing the selection set to use a function.Was this intentional? Should I invest time in figuring out a way to update my queries or is there other ways to use
UTC
by default? Should I convert my timestamps to UTC after fetching them as Go types?Client
e.g. BigQuery
Environment
Local installation / Any
Go Environment
Code
Expected behavior
The data returned by the client to be the same in v1.58.0 and v1.59.0
Actual behavior
The data is no longer the same, it now holds a local timezone instead of UTC.
Screenshots
n/a
Additional context
Started after upgrading to v1.59.0. Most likely in #9368 and this line.
The text was updated successfully, but these errors were encountered: