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

add coalesce to min start_date for date_spine in case stg_distribution_contact is empty #6

Merged
merged 5 commits into from
Dec 20, 2023

Conversation

fivetran-jamie
Copy link
Contributor

@fivetran-jamie fivetran-jamie commented Dec 19, 2023

Are you a current Fivetran customer?

internal

What change(s) does this PR introduce?

addresses issue #5

Bug Fix

  • Ensures that date spine in qualtrics__daily_breakdown always has a non-null start date, even if you do not have the distribution_contact source table, whose min(created_at) we base the date spine off of.
    • If no distribution_contact table is present in your Qualtrics connector(s), the minimum date will be set to 2016-01-01.

Under the Hood

  • Updated the pull request templates.
  • Included auto-releaser GitHub Actions workflow to automate future releases.

Did you update the CHANGELOG?

  • Yes

Does this PR introduce a breaking change?

  • Yes (please provide breaking change details below.)
  • No (please provide an explanation as to how the change is non-breaking below.)

Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)

  • Yes

Is this PR in response to a previously created Bug or Feature Request

How did you test the PR changes?

  • Buildkite
  • Local (please provide additional testing details below)

See Hex notebook linked in Height task

Select which warehouse(s) were used to test the PR

  • BigQuery
  • Redshift
  • Snowflake
  • Postgres
  • Databricks
  • Other (provide details below)

Provide an emoji that best describes your current mood

🏂

Feedback

We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.

Copy link
Collaborator

@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-jamie thanks for quickly addressing this issue! Given your validations and my review, this looks good to me!

I did have one call out below for a reminder when adding the auto releaser to a repo, and also a suggestion to adjust the wording in the CHANGELOG. Other than that, this looks good to go!

@@ -0,0 +1,13 @@
name: 'auto release'
Copy link
Collaborator

Choose a reason for hiding this comment

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

Thanks for adding this! FYI don't forget to add the GH_SECRET when you are adding this workflow into a package pipeline.

I just added it for this repo, but it will need to be manually added in the repo settings each time we add this action.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

doh right, thanks for adding it

CHANGELOG.md Outdated Show resolved Hide resolved
Co-authored-by: Joe Markiewicz <[email protected]>
@fivetran-jamie fivetran-jamie merged commit 84a7171 into main Dec 20, 2023
1 check passed
@fivetran-jamie fivetran-jamie deleted the bug/min-date-spine-date branch December 20, 2023 17:26
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.

2 participants