Bugfix/duplicate columns

[fivetran-joemarkiewicz]

PR Overview

This PR will address the following Issue/Feature: dbt_hubspot Issue 119

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

This will technically be a breaking change since it will remove (via a coalesce) existing impacted fields if duplicates are identified. As such, I would feel more comfortable with this being a breaking change so customers are aware of the upgrade being applied.

Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:

🚨 Breaking Changes 🚨

• The following models have received an update to leverage a new custom macro to remove the prefix property_hs_ prefix from the source columns in the staging models. If a column with the prefix removed matches the same name as an existing column (for example property_hs_meeting_outcome and meeting_outcome are both fields in the source table), then the new macro will coalesce the fields giving preference to the property_hs_ field as this is likely the most relevant field per the latest HubSpot API upgrade.
  • stg_hubspot__engagement_call
  • stg_hubspot__engagement_company
  • stg_hubspot__engagement_contact
  • stg_hubspot__engagement_deal
  • stg_hubspot__engagement_email
  • stg_hubspot__engagement_meeting
  • stg_hubspot__engagement_note
  • stg_hubspot__engagement_task
  • stg_hubspot__ticket
  • stg_hubspot__ticket_company
  • stg_hubspot__ticket_contact
  • stg_hubspot__ticket_deal
  • stg_hubspot__ticket_engagement
  • stg_hubspot__ticket_property_history

Feature Updates

• A new macro remove_duplicate_and_prefix_from_columns has been included which expands off the fivetran_utils.remove_prefix_columns macro by removing any duplicate columns that result from the prefix removal.

PR Checklist

Basic Validation

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

• [X] dbt compile
• [X] dbt run –full-refresh
• [X] dbt run
• [X] dbt test
• [n/a] dbt run –vars (if applicable)

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

• [X] The appropriate issue has been linked and tagged
• [X] You are assigned to the corresponding issue and this PR
• [x] BuildKite integration tests are passing

Detailed Validation

Please acknowledge that the following validation checks have been performed prior to marking this PR as "ready for review":

• [X] You have validated these changes and assure this PR will address the respective Issue/Feature.
• [X] You are reasonably confident these changes will not impact any other components of this package or any dependent packages.
• [X] You have provided details below around the validation steps performed to gain confidence in these changes.

These steps were validated by recreating the issue with the seed data for our integration tests and also via validation with the customer that the fix does in fact resolve the error they are seeing.

Standard Updates

Please acknowledge that your PR contains the following standard updates:

• Package versioning has been appropriately indexed in the following locations:
  • [X] indexed within dbt_project.yml
  • [X] indexed within integration_tests/dbt_project.yml
• [X] CHANGELOG has individual entries for each respective change in this PR
• [X] README updates have been applied (if applicable)
• [n/a] DECISIONLOG updates have been updated (if applicable)
• [n/a] Appropriate yml documentation has been added (if applicable)

dbt Docs

Please acknowledge that after the above were all completed the below were applied to your branch:

• [X] docs were regenerated (unless this PR does not include any code or yml updates)

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

2️⃣

[fivetran-joemarkiewicz]

Thanks much! Will it be released soon?

I am very close to releasing this! Likely Monday morning at this point. I heard from our product team that these additional fields (the non property_hs_ fields) were due to a bug in the connector and we may want to ignore the non property_hs_ fields altogether. I am just waiting on confirmation from our product team if I should keep the coalesce or remove it entirely.

[greg-finley]

Thanks much! Will it be released soon?

I am very close to releasing this! Likely Monday morning at this point. I heard from our product team that these additional fields (the non property_hs_ fields) were due to a bug in the connector and we may want to ignore the non property_hs_ fields altogether. I am just waiting on confirmation from our product team if I should keep the coalesce or remove it entirely.

From looking at my own data, they seem to be all nulls, so I think removing or coalescing would have the same effect (though I guess slightly more efficient to avoid the coalesce)