Add Source Freshness Results #437
Open
Conversation
This file contains hidden or 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
dpguthrie
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
dpguthrie
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
dpguthrie
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
dpguthrie
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
temporarily deployed
to
Approve Integration Tests
GitHub Actions
Inactive
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
temporarily deployed
to
Approve Integration Tests
GitHub Actions
Inactive
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
temporarily deployed
to
Approve Integration Tests
GitHub Actions
Inactive
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
temporarily deployed
to
Approve Integration Tests
GitHub Actions
Inactive
llifoawing
temporarily deployed
to
Approve Integration Tests
GitHub Actions
Inactive
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
temporarily deployed
to
Approve Integration Tests
GitHub Actions
Inactive
llifoawing
temporarily deployed
to
Approve Integration Tests
GitHub Actions
Inactive
llifoawing
temporarily deployed
to
Approve Integration Tests
GitHub Actions
Inactive
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
llifoawing
temporarily deployed
to
Approve Integration Tests
GitHub Actions
Inactive
llifoawing
had a problem deploying
to
Approve Integration Tests
GitHub Actions
Failure
|
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 ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
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
Resultsobject will be populated with SourceFreshnessResults. The behavior is very similar to all of the other_executionstables/models.Update type - breaking / non-breaking
What does this solve?
#166
Outstanding questions
The schema is slightly different than all of the other
_executionstables. 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?