Enable package to use Snowflake Organisation Account views #178
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bisset-a
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support of views in the new Snowflake organisation account, while still being compatible with single account Snowflake views.
To use the dbt_snowflake_monitoring package in multi-account mode, Project variable uses_org_view should be set to true in the downstream project.
Notes
When using org account views, query acceleration is not baked into cost per query. This is because the metering_history view is not currently available in the organisation account. Snowflake have confirmed it will be available in Q2 (May - July) so right now we are making a pragmatic decision to exclude QA from the query cost calculation until this view is enabled.
models hourly_spend and daily_spend do not include serverless task spend. This is because severless_task_history does not exist in the organisation account. Snowflake confirmed this will be enabled in Q2 aswell.