-
Notifications
You must be signed in to change notification settings - Fork 85
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 Storage Write API: ISO 8601 timestamp not supported in JsonStreamWriter #1580
Comments
@geirsagberg my issue is very similar even if the incorrect format is use it will still parse it into gibberish, |
@dark0dave upon some more testing, looks like the formats commented out below don't work: Could you take a look at adding more support? |
@stephaniewang526 yes will fix. |
@stephaniewang526 this is not ISO compilant:
This is the iso standard below: https://en.wikipedia.org/wiki/ISO_8601 Big Query's own format, for timestamps are as follows: YYYY-[M]M-[D]D[( |T)[H]H:[M]M:[S]S[.F]][time zone] Taken from the Big Query docs: https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types#timestamp_type Which does not support this, format. I have tried to follow Big Query does best I can in parsing, but this format I do not feel the need to support as its not ISO. |
Additionally, I don't think I want to allow for doubles or floats to be parsed as they are not exact at all. Doesn't really seem like a good TIMESTAMP value, which are supposed to point to exact moments in time. |
oh wow. Interesting. |
Can you provide a link to that please? |
thanks @stephaniewang526, let me update my pr. |
@stephaniewang526 all done, all formats you have described have been added as tests |
Environment details
General, Core, and Other are also allowed as types
implementation("com.google.cloud", "google-cloud-bigquerystorage", "2.11.0")
Steps to reproduce
JsonStreamWriter
2022-03-16T13:00:00Z
Code example
Stack trace
API reference
According to https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types#timestamp_type ISO8601 string should be supported.
Any additional information below
Would also be helpful to be able to encode timestamp as ISO8601 string in protobuf.
The text was updated successfully, but these errors were encountered: