-
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: Add StandardSqlDataTypes enum to BigQuery #8782
Conversation
Looks like we might need to pin one of the dependencies (pyarrow?) to fix our tests. |
Yeah, I've already been discussing this with @tswast, it's how pyarrow (?) handles |
This is a convenience enum that contains scalar SQL data types constants (a subsset of types defined in the gapic enum generated from the .proto definitions).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM once the docs update is in.
@@ -130,6 +131,7 @@ | |||
"Encoding", | |||
"QueryPriority", | |||
"SchemaUpdateOption", | |||
"StandardSqlDataTypes", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This reminds me: let's add an Enums section to the API reference docs, too.
https://github.com/googleapis/google-cloud-python/blob/master/bigquery/docs/reference.rst
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added. Also had to inject an additional header line to the new enum's docstring, because Sphinx complained about a duplicate object description (took the first line - the INT64 member - which is of course directly copied from the gapic enum).
Closes #8495.
This PR adds a convenience enum with scalar SQL data types (as per issue description).
How to test
The issue is self-explanatory. Just make sure that the enum contains all the right fields that we want in it.
Update: Additionally, make sure that the docs for the new enum are in order.