ntd: define mart schema in dbt project for funding and expenses tables #3689
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
evansiroky
approved these changes
Feb 12, 2025
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
We created warehouse tables for the NTD funding and expenses endpoints in #3665 but neglected to define the mart schema in the dbt_project.yml file, so by default they populated in the staging schema, as noticed by @evansiroky. This PR defines the schema for these tables as
mart_ntd_funding_and_expensesand they will now appear in Bigquery as such.Type of change
How has this been tested?
Post-merge follow-ups