-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 parity for statement blocks #526
Conversation
dbt/context/common.py
Outdated
logger.debug(msg) | ||
def log(msg, info=False): | ||
if info: | ||
logger.info(" ↳ " + msg) |
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.
@cmcarthur i really like this but fear that it will randomly break python2 installations. Will remove
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.
oh lol yeah it broke circle
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.
one very minor change. this looks great.
dbt/adapters/default.py
Outdated
else: | ||
_, cursor = cls.execute_one(profile, sql, model_name, auto_begin) | ||
status = cls.get_status(cursor) | ||
return status, None |
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.
default result data was []
, now it's None
I really like this approach but I think we should condense the execute
/ execute_one
/ execute_and_fetch
/ add_query
APIs into a smaller set of functions. Not blocking for this PR.
This branch makes the statement block work with the bigquery adapter. This is necessary for implementing introspective materializations which run against bigquery.
TODO: