NTD: materialize marts as tables and add handling for report_year field #3603
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
charlie-costanzo
added
the
data-pipeline-ingestion-and-modeling
charlie-costanzo
requested review from
evansiroky,
vevetron and
tiffanychu90
as code owners
|
Warehouse report 📦 DAGLegend (in order of precedence)
|
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.
Description
Following up in our MVP ingestion of NTD tables, this PR materializes our NTD mart data as tables and handles the report_year field as an integer in tables where relevant.
Type of change
How has this been tested?
Post-merge follow-ups