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

bugfix/string-agg-removal #119

Merged
merged 7 commits into from
Mar 18, 2024
Merged

Conversation

fivetran-joemarkiewicz
Copy link
Contributor

@fivetran-joemarkiewicz fivetran-joemarkiewicz commented Mar 14, 2024

PR Overview

This PR will address the following Issue/Feature: Issue #118

This PR will result in the following new package version: v1.7.0

This will be a breaking change as we are removing fields from an end model and could cause downstream errors with their removal.

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

🚨 Breaking Changes 🚨: Bug Fixes

  • The following fields have been deprecated (removed) as these fields proved to be problematic across warehouses due to the end size of the fields.
    • errors_since_last_completed_sync
    • warnings_since_last_completed_sync

Note: If you found these fields to be relevant, you may still reference the error/warning messages from within the underlying log table.

  • The fivetran_platform_using_sync_alert_messages variable has been removed as it is no longer necessary due to the above changes.

Feature Updates

  • The following fields have been added to display the number of error/warning messages sync last completed sync. These fields are intended to substitute the information from deprecated fields listed above.
    • number_errors_since_last_completed_sync
    • number_warnings_since_last_completed_sync

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:

Please see the corresponding Height ticket for a link to the Hex document that includes the Hex validations notebook.

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

🔢

@fivetran-joemarkiewicz fivetran-joemarkiewicz marked this pull request as ready for review March 15, 2024 15:24
README.md Outdated Show resolved Hide resolved
Copy link
Contributor

@fivetran-reneeli fivetran-reneeli left a comment

Choose a reason for hiding this comment

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

Reviewed with a few suggestions/ question!

@fivetran-joemarkiewicz
Copy link
Contributor Author

Thanks @fivetran-reneeli for the quick and thoughtful review! I just addressed your comments and committed your suggestions. Thanks for catching my spelling mistakes 🤦. I also addressed the open question you had and will hold off regenerating the docs until approval.

@fivetran-reneeli
Copy link
Contributor

Thanks @fivetran-joemarkiewicz , just responded above!

@fivetran-joemarkiewicz
Copy link
Contributor Author

@fivetran-reneeli thanks again! I agree with your comment and just applied the changes and regenerated the docs. Let me know if you have any other comments.

Copy link
Contributor

@fivetran-reneeli fivetran-reneeli left a comment

Choose a reason for hiding this comment

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

lgtm

@fivetran-joemarkiewicz fivetran-joemarkiewicz merged commit 1856dd4 into main Mar 18, 2024
9 checks passed
@fivetran-joemarkiewicz fivetran-joemarkiewicz deleted the bugfix/string-agg-removal branch March 18, 2024 14:45
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