-
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 enum with SQL type names allowed to be used in SchemaField #9040
Conversation
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.
Thanks. Yeah, just string values for these.
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.
Oops. Actually, looks like we're missing GEOGRAPHY.
@tswast GEOGRAPHY is not listed among the legacy types. Am I missing something? Edit: The ticket description is somewhat ambiguous - I will add the string names names of the standard SQL types, too (as the issue title suggests), since that was probably the goal. |
Thanks. Yes, all standard SQL types names are aliases in legacy SQL, so I think that makes sense. Filed b/139704786 to document GEOGRAPHY as not supported in legacy SQL, but still a valid type where legacy SQL names are expected in the API. |
…eld (googleapis#9040) * Add enum with legacy SQL type names * Add standard types to enum, rename enum
Closes #7632.
This PR adds an enum of legacy SQL type names that can be used with in schema fields.
@tswast This enum is a bit different from the existing
StandardSqlDataTypes
enum which maps type names to their gapic integer codes. Let me know if I misunderstood the ticket.How to test
Make sure all of the legacy SQL type names are included in the enum (and nothing else).