brooklyn-data
Add Source Freshness Results
Overview
This PR adds source freshness executions to the package. This was recently added into dbt-core and now if the user opts into this behavior (adding a specific flag in their dbt_project.yml file), the Results object will be populated with SourceFreshnessResults. The behavior is very similar to all of the other _executions tables/models.
Update type - breaking / non-breaking
- [ ] Minor bug fix
- [ ] Documentation improvements
- [ ] Quality of Life improvements
- [x] New features (non-breaking change)
- [ ] New features (breaking change)
- [ ] Other (non-breaking change)
- [ ] Other (breaking change)
- [ ] Release preparation
What does this solve?
#166
Outstanding questions
The schema is slightly different than all of the other _executions tables. Happy to change that, it just seemed that 1) some of the info wasn't relevant and 2) there's additional info we need to capture.
What databases have you tested with?
- [x] Snowflake
- [ ] Google BigQuery
- [x] Databricks
- [ ] Spark
- [ ] N/A
Looks like the integration test failures on this PR appear to be somewhat similar to those seen on this bug: #488. Is it fair to assume that this PR may actually be blocked based on an upstream regression?
Looks like the integration test failures on this PR appear to be somewhat similar to those seen on this bug: #488. Is it fair to assume that this PR may actually be blocked based on an upstream regression?
I see you were a lot involved in that feature. Do you plan to fix the remaining bugs ? Thanks a lot !
