--
You received this message because you are subscribed to the Google Groups "Google Cloud Bigtable Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-bigtable-discuss+unsub...@googlegroups.com.
To post to this group, send email to google-cloud-bigtable-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-bigtable-discuss/ed09da79-982c-47b8-af13-946d36733c73%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Wed, Jul 18, 2018 at 1:39 PM, lou.loizides via Google Cloud Bigtable Discuss <google-cloud-bigtable-dis...@googlegroups.com> wrote:
The date/time strings we're sending over to pub/sub look like this:2018-07-18T17:30:08ZI created a data flow job to insert these into Big Query and it failed at insert.Stripping out the "Z" at the end like this was successful:2018-07-18T17:30:08The problem is that Big Query seems to be interpreting this as a local time, and not UTC.I've tried both of these ways to insert the time zone:2018-07-18T17:30:08+00:002018-07-18T17:30:08+0000Both are rejected.What's the correct way to do this, or is there some other way I can force Big Query to interpret these times as UTC?
--
You received this message because you are subscribed to the Google Groups "Google Cloud Bigtable Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-bigtable-discuss+unsub...@googlegroups.com.
To post to this group, send email to google-cloud-b...@googlegroups.com.