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

Fix _get_cache_schemas by removing relation identifiers #53

Merged
merged 3 commits into from
Jan 26, 2024

Conversation

jtcohen6
Copy link
Contributor

resolves #52

Problem

We were running one caching query per relation (resource) defined in the project

Solution

We should only run one caching query per schema, by dropping the relation-specific identifier within _get_cache_schemas

Checklist

  • I have read the contributing guide and understand what's expected of me
  • I have run this code in development and it appears to resolve the stated issue
  • This PR includes tests, or tests are not required/relevant for this PR
  • This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

@mikealfare mikealfare merged commit 60005a0 into main Jan 26, 2024
5 checks passed
@mikealfare mikealfare deleted the jerco/fix-52 branch January 26, 2024 17:32
@colin-rogers-dbt colin-rogers-dbt mentioned this pull request Jan 30, 2024
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] dbt commands running the same metadata query way too many times
3 participants