Skip to content
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

Merged
merged 4 commits into from
Jun 17, 2024
Merged

Conversation

fivetran-catfritz
Copy link
Contributor

@fivetran-catfritz fivetran-catfritz commented Jun 12, 2024

PR Overview

This PR will address the following Issue/Feature:

This PR will result in the following new package version:

  • v1.0.2: patch update since updating logic but no schema changes

Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:

Bug fixes

  • Updated model int_salesforce__date_spine to accommodate when model salesforce__lead exists but has no records. In this case, the model now defaults to a range of one-month from the current date.

Under the hood

  • Updated structure of model int_salesforce__date_spine for improved performance and maintainability.
  • Updated maintainer pull request template.

PR Checklist

Basic Validation

Please acknowledge that you have successfully performed the following commands locally:

  • dbt run –full-refresh && dbt test
  • dbt run (if incremental models are present) && dbt test

Before marking this PR as "ready for review" the following have been applied:

  • The appropriate issue has been linked, tagged, and properly assigned
  • All necessary documentation and version upgrades have been applied
  • docs were regenerated (unless this PR does not include any code or yml updates)
  • BuildKite integration tests are passing
  • Detailed validation steps have been provided below

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:

Screenshot 2024-06-12 at 4 05 09 PM
  • The updates to this package resolve the error and produce the expected spine range:
Screenshot 2024-06-12 at 3 55 38 PM

If you had to summarize this PR in an emoji, which would it be?

🐰

@fivetran-catfritz fivetran-catfritz changed the title ug/spine-empty-lead-update bug/spine-empty-lead-update Jun 12, 2024
@fivetran-catfritz fivetran-catfritz self-assigned this Jun 12, 2024
final as (
-- test will fail if any rows from prod are not found in dev
(select * from prod
except distinct
Copy link
Contributor

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

Copy link
Contributor

@fivetran-jamie fivetran-jamie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Copy link
Contributor

@fivetran-joemarkiewicz fivetran-joemarkiewicz left a 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.

CHANGELOG.md Outdated Show resolved Hide resolved
Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com>
@fivetran-catfritz fivetran-catfritz merged commit 614880a into main Jun 17, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants