-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BigQuery] Can't insert correct TIMESTAMP. #1247
Comments
I suspect that here is the cause. ref: https://cloud.google.com/bigquery/preparing-data-for-bigquery?hl=en#datatypes |
Totally agree. @tseaver and I had a discussion about this before and we thought we had a found a decisive place indicating how the value should be sent. It seems we got it wrong. |
Thank you for your comment! |
I can't say 100% it's a bug, but it seems pretty likely. It means we'll dig into verifying and then fixing if we can find a verifiable bug. (Again seems very likely.) |
OK, I got it. I hope it's fixed. 😄 |
@kamatama41 The docs you link above state:
So, rather than passing milliseconds, we should just pass seconds. |
FYI @tseaver I am fixing this right now |
I'm also finding lots of out-of-date docs in http://gcloud-python.readthedocs.org/en/latest/bigquery-usage.html |
What if we want to store millisec sensitive data here? Like sensors data that are collected at more than 1 Hz |
@kalanyuz This issue was closed by a PR which correctly Python datetime objects into |
In my environment, I can't insert correct data to the
TIMESTAMP
column.The following snippet is the smallest reproducible example.
Please let me know that it's a bug or my mistake.
The text was updated successfully, but these errors were encountered: