This PR is a companion to one created by @fivetran-joemarkiewicz to resolve possible build failures that may occur when syncing certain HubSpot tables that do not have any recorded deletion events.
Fivetran lists the tables that they 'Capture deletes' for here: https://fivetran.com/docs/applications/hubspot
and this PR resolves a problem that can occur in the modeling of tickets since hubspot does not explicitly support the is_deleted column.
Did you update the CHANGELOG?
[ ] Yes
[x] No (I wasn't sure how to handle the versioning but am happy to add a commit for this if needed)
Does this PR introduce a breaking change?
[ ] Yes (please provide breaking change details below.)
[x] No (please provide an explanation as to how the change is non-breaking below.)
This change in conjunction with the other one mentioned above should resolve build issues for certain users but it does not change the performance of the model nor does it break any dependencies.
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
[x] No (I wasn't sure how to handle the versioning but am happy to add a commit for this if needed)
Is this PR in response to a previously created Bug or Feature Request
[ ] Yes, Issue/Feature [link bug/feature number here]
[x] No
How did you test the PR changes?
[ ] CircleCi
[x] Local (please provide additional testing details below)
I tested this change locally on my own dbt project. I experienced no issues and no noticeable performance degradation.
Select which warehouse(s) were used to test the PR
[ ] BigQuery
[ ] Redshift
[ ] Snowflake
[x] Postgres
[ ] Databricks
[ ] Other (provide details below)
Provide an emoji that best describes your current mood
:dancer:
**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](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next.
Pull Request Are you a current Fivetran customer?
Sam B. -- Data Analyst -- Unchained Capital
What change(s) does this PR introduce?
This PR is a companion to one created by @fivetran-joemarkiewicz to resolve possible build failures that may occur when syncing certain HubSpot tables that do not have any recorded deletion events. Fivetran lists the tables that they 'Capture deletes' for here: https://fivetran.com/docs/applications/hubspot and this PR resolves a problem that can occur in the modeling of tickets since hubspot does not explicitly support the is_deleted column.
Did you update the CHANGELOG?
Does this PR introduce a breaking change?
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)
Is this PR in response to a previously created Bug or Feature Request
How did you test the PR changes?
Select which warehouse(s) were used to test the PR
Provide an emoji that best describes your current mood
:dancer: **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](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next.