bugfix/timestamp-without-time-zone

[fivetran-joemarkiewicz]

PR Overview

This PR will address the following Issue/Feature: Internally raised Issue

This PR will result in the following new package version: v0.2.0

This likely won't be breaking for the majority of users. However, this will be changing the datatypes of a number of fields to timestamp without time zone; whereas, before they were timestamp with time zone. Therefore, we will mark this as breaking.

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

🚨 Breaking Changes: Bug Fixes 🚨

• Casted the following timestamp fields in the below models using the dbt.type_timestamp() macro. This is necessary to ensure all timestamps are consistently casted and do not experience datatype mismatches in downstream transformations.
  • stg_qualtrics__contact_mailing_list_membership
    • unsubscribed_at
  • stg_qualtrics__directory_contact
    • created_at
    • unsubscribed_from_directory_at
    • last_modified_at
  • stg_qualtrics__directory_mailing_list
    • created_at
    • last_modified_at
  • stg_qualtrics__distribution_contact
    • opened_at
    • response_completed_at
    • response_started_at
    • sent_at
  • stg_qualtrics__distribution
    • created_at
    • last_modified_at
    • send_at
    • survey_link_expires_at
  • stg_qualtrics__survey_response
    • finished_at
    • is_finished
    • last_modified_at
    • recorded_date
    • started_at
  • stg_qualtrics__survey_version
    • created_at
  • stg_qualtrics__survey
    • last_accessed_at
    • last_activated_at
    • last_modified_at
  • stg_qualtrics__user
    • account_created_at
    • account_expires_at
    • last_login_at
    • password_expires_at
    • password_last_changed_at

Please note: this update will likely only impact Redshift destinations as it was found the connector synced these fields as timestamp with time zone when in fact they were without. Most users will not see any changes following this release. But we marked this as breaking to ensure no possible datatype conflicts downstream.

Under the Hood

• Updated the maintainer PR template to resemble the most up to date format.
• Added the auto release GitHub Action for easier deployment.

PR Checklist

Basic Validation

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

• [X] dbt run –full-refresh && dbt test
• [n/a] dbt run (if incremental models are present)

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

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

Detailed Validation

Please share any and all of your validation steps:

None of these changes really need any validating in the source package, so the core of the validation is done in combination with the downstream dbt_qualtrics package.

First I recreated the issue by setting up a new Qualtrics connector (for Redshift) and attempted to use the production version of the package. Alas, I saw the same error as documented:

I then installed the local version of the qualtrics package with these changes included and saw the errors resolved!

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

⏲️