René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"BigQuery python cli fails to change time, BUT does changes timezone for TIMESTAMP which leads to an incorrect time","articleBody":"This code works with with the python package\r\n   **google-cloud-bigquery==2.2.0** \r\nbut it does not work with this package\r\n   **google-cloud-bigquery==2.6.0**\r\n\r\nWhat you expected to happen:\r\n\r\nI expect the client library to take a datetime of\r\n '_2017-11-01 04:08 AM -07:00_'    and convert it to\r\n '_2017-11-01 11:08 AM -00:00_' in big query. but instead it uploads it to\r\n '_2017-11-01 04:08 AM -00:00_'\r\n\r\nSteps to reproduce:\r\n```\r\nimport datetime\r\nfrom dateutil.tz import tzoffset\r\nfrom google.cloud.bigquery import SchemaField, Table\r\n\r\nschema = [SchemaField('c', 'TIMESTAMP', 'NULLABLE', None, (), None)] \r\nproblem_date = datetime.datetime(2017, 11, 1, 4, 8, tzinfo=tzoffset(None, -25200))\r\ntable_name = ‘my_test_table’\r\ndataset = \u003can existing dataset\u003e\r\n\r\nbigquery = bigquery.Client(credentials=\u003csomecreds\u003e, project=\u003courproj\u003e)\r\n\r\ndataset_ref = bigquery.dataset(dataset, project=\u003courproj\u003e)\r\ntable_ref = dataset_ref.table(table_name)\r\ntable = bigquery.create_table(Table(table_ref, schema=schema))\r\nerrors = bigquery.insert_rows(table, [[problem_date]])\r\n```\r\n\r\n#### Other info\r\n-------------------------------\r\nI worked with the google BigQuery team and here is their [feedback](https://issuetracker.google.com/issues/175849093).\r\nHello,\r\n\r\nI have been investigating the issue you described and it seems like this change of behaviour of the python client library was introduced in the version 2.5.0 [1] with the pull request #393 [2], whose objective was to fix a previous issue with floating points and timestamps in the method `insert_rows`.\r\n\r\nI have been able to reproduce your issue in new versions after 2.5.0 while it does not happen in the previous ones. The suggested way to proceed here would be to open an issue in the Github repository [3] so you can transmit your findings to the Engineering Team, since the code is open source .\r\n\r\nAlternatively, you might want to add the following line of code, so the timezone is converted to UTC before trying to insert the row into BigQuery. Please let me know if this workaround worked for you:\r\n```\r\nproblem_date = datetime.datetime(2017, 11, 1, 4, 8, tzinfo=tzoffset(None, -25200))\r\nproblem_date = problem_date.astimezone(datetime.timezone.utc)\r\n```\r\n\r\n[1]:\r\nhttps://github.com/googleapis/python-bigquery/releases/tag/v2.5.0\r\n[2]:\r\nhttps://github.com/googleapis/python-bigquery/pull/393\r\n[3]:\r\nhttps://github.com/googleapis/python-bigquery/issues\r\n\r\n-------------------------------\r\n\r\nWe will look into the feasibility of the workaround\r\n\r\n\r\n","author":{"url":"https://github.com/zsolt-sb","@type":"Person","name":"zsolt-sb"},"datePublished":"2021-01-19T17:18:39.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/476/python-bigquery/issues/476"}