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.
Summary
Production nightly runs have been successful so far. I added logging early on to output metadata throughout every step in the pipeline; however, the metadata aren't tied to asset checks outside of dbt. I checked the logs, and saw that the size of the cycling data from model training was less than 600 activities (in the
cycling_data
asset). Since this is my personal data, I knew to expect +1000 activities so the data is obviously wrong. This PR addresses this issue.Note: This also prompts a future feature need for backfilling capabilities in the dltHub pipeline in the context of dagster.
Details
Source of the issue
__src_schema.yml
Additions:
minor updates to dbt models / duckdb query
add custom dbt tests in
analytics_dbt/tests/
analytics_dbt/tests/test_activity_counts.sql
analytics_dbt/tests/test_cycling_counts.sql
add dagster
asset_checks
for cycling_data