-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 support for non-legacy SQL #1896
Conversation
@ukarlsson, thanks for your PR! By analyzing the history of the files in this pull request, we identified @mikekap, @mbruggmann and @jpotts18 to be potential reviewers. |
def use_legacy_sql(self): | ||
"""Whether to use legacy SQL | ||
""" | ||
return True |
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.
Is using legacy default o_O?
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.
Hey, sorry had forgot about this PR, yes legacy should be default in order not to break compatibility, it is also still default in the BigQuery console
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.
Perhaps we can merge PR
@ukarlsson, I would love to merge this, but can you get someone else who knows BigQuery to review this? |
@Tarrasch We are running something very similar internally as well. Not sure if that qualifies as "knowing BigQuery" but I'd give this a 👍 |
@mbruggmann, certainly good enough for me (that you run it in production). Thanks for reviewing. :) |
No description provided.