-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug/spine-empty-lead-update #52
Conversation
final as ( | ||
-- test will fail if any rows from prod are not found in dev | ||
(select * from prod | ||
except distinct |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ooh la la what's this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fivetran-catfritz this looks great from my end! Just one suggestion to make a small change in the CHANGELOG. Let me know if I misinterpreted your originally wording.
Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com>
PR Overview
This PR will address the following Issue/Feature:
int_salesforce__date_spine
- use current_date #49This PR will result in the following new package version:
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
dbt run (if incremental models are present) && dbt testBefore marking this PR as "ready for review" the following have been applied:
Detailed Validation
Please share any and all of your validation steps:
For reference, changes are very similar to those I made in v0.13.0 stripe.
Created consistency and integrity tests for the direct downstream model
salesforce__daily_activity
, which all pass when run on our internal data.I was able to reproduce the issue by supplying an empty lead seed table. Running on the current version produces this error:
If you had to summarize this PR in an emoji, which would it be?
🐰