Skip to content
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

[Backport] #3716 to v0.20.2, too #3809

Merged
merged 1 commit into from
Aug 26, 2021
Merged

Conversation

jtcohen6
Copy link
Contributor

As initially reported, #3715 was a cosmetic issue that resulted in some failed Snowflake queries, but no failed dbt runs. I've now heard reports from some users of other databases that don't have handling when dbt tries to cache (grab metadata for) a nonexistent schema (main Slack thread here).

This is definitely a fix for something v0.20-related. Now that I understand the bug is functional, not just cosmetic, I think it belongs in v0.20.2. The question if whether we'd want some extra testing and validation before final release—i.e. a second release candidate, v0.20.2-rc2, now that we've got a handful of changes since the last one.

@jtcohen6 jtcohen6 requested a review from leahwicz August 25, 2021 17:37
@cla-bot cla-bot bot added the cla:yes label Aug 25, 2021
@kwigley
Copy link
Contributor

kwigley commented Aug 25, 2021

@jtcohen6 #3807 will fix the failing postgres test here!

* Use is_relational check for schema caching

* Fix flake8

* Update changelog
@kwigley kwigley force-pushed the backport-3716-to-020 branch from 75baf6f to 57d0e21 Compare August 25, 2021 18:29
@jtcohen6 jtcohen6 merged commit 3cd8711 into 0.20.latest Aug 26, 2021
@jtcohen6 jtcohen6 deleted the backport-3716-to-020 branch August 26, 2021 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants