-
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] Option to set useLegacySql
to false on queries
#1927
Labels
api: bigquery
Issues related to the BigQuery API.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Comments
@kelvinabrokwa Thanks for the report! We'd be glad to review / merge a PR for that feature. |
tseaver
added
the
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
label
Jun 28, 2016
@tseaver I can tackle this, sound good? |
@dhermes Sure, if @kelvinabrokwa doesn't already have it in progress. |
@dhermes go for it! 😄 |
@dhermes any progress? |
Doing it now. Sorry for the delay. |
@dhermes no worries! Thank you! 😄 |
Via #1992. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
api: bigquery
Issues related to the BigQuery API.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
My use case here is that there is a certain query that errors on legacy SQL (internal bug) and disabling it will allow the use of standard SQL which fixes it.
see https://cloud.google.com/bigquery/docs/reference/v2/jobs#resource-representations (find
configuration.query.useLegacySql
)I'm happy to submit a PR is this option makes sense.
The text was updated successfully, but these errors were encountered: