refactor!: Move materialized views to dbt #547
Merged
Conversation
This file contains 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
This change allows deeper configuration of the 2nd order schema via extending or overriding the materialized views.
bmtcril
force-pushed
the
bmtcril/move_mvs_to_dbt_and_squash
branch
from
0f9041a to
d2d9b88
Compare
3.0 didn't have the latest version of xapi_events_all_parsed_mv, this fixes that
Ian2012
approved these changes
Dec 19, 2023
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 change allows deeper configuration of the 2nd order schema via extending or overriding the materialized views. Note that this will currently rebuild all materialized view tables on dbt run / aspects init. See this issue for details on how we plan to fix it: #546
Closes #533
Closes #543
Closes #548