You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, in the hubspot__contacts.sql model that exists in this package the CONTACT_MERGE_AUDIT table is still being referenced if hubspot_contact_merge_audit_enabled is marked as True in dbt_project.yml. Since most users moving forward will not have the CONTACT_MERGE_AUDIT in their schema, hubspot_contact_merge_audit_enabled should have a default of False.
Relevant error log or model output
No response
Expected behavior
Since most users moving forward will not have the CONTACT_MERGE_AUDIT in their schema, hubspot_contact_merge_audit_enabled should have a default of False.
dbt Project configurations
They are configured to the default settings.
Package versions
n/a
What database are you using dbt with?
bigquery
dbt Version
n/a
Additional Context
No response
Are you willing to open a PR to help address this issue?
Yes.
Yes, but I will need assistance and will schedule time during our office hours for guidance
No.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Describe the issue
Per the HubSpot Release Notes, Fivetran deprecated the
CONTACT_MERGE_AUDIT
table.However, in the hubspot__contacts.sql model that exists in this package the
CONTACT_MERGE_AUDIT
table is still being referenced ifhubspot_contact_merge_audit_enabled
is marked asTrue
in dbt_project.yml. Since most users moving forward will not have theCONTACT_MERGE_AUDIT
in their schema,hubspot_contact_merge_audit_enabled
should have a default ofFalse
.Relevant error log or model output
No response
Expected behavior
Since most users moving forward will not have the
CONTACT_MERGE_AUDIT
in their schema,hubspot_contact_merge_audit_enabled
should have a default ofFalse
.dbt Project configurations
They are configured to the default settings.
Package versions
n/a
What database are you using dbt with?
bigquery
dbt Version
n/a
Additional Context
No response
Are you willing to open a PR to help address this issue?
The text was updated successfully, but these errors were encountered: