[Bug] Fix concatenation issue with null values creating null rows in Snowflake

[fivetran-avinash]

PR Overview

This PR will address the following Issue/Feature: [#20]

This PR will result in the following new package version: v0.1.0-a6

This ensures null fields gets populated but shouldn't change the schema.

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

Bug Fixes (requires --full-refresh)

• Applied coalesce_cast macro to all relevant fields that are being concatenated into comment_markdown, as any concatenation in Snowflake with a null value returns null. We coalesced 'UNKNOWN' on a string field, and '1970-01-01 00:00:00' on a timestamp field to ensure Snowflake returns chunks of texts for all comments with null components.
• Fields are now coalesced in these intermediate models:
  • Hubspot
    • int_rag_hubspot__deal_comment_document: email_title and body (string fields), comment_time (timestamp field).
    • int_rag_hubspot__deal_document: title (string field) and created_on (timestamp field).
  • Jira
    • int_rag_jira__issue_comment_document: comment_body (string field) and comment_time (timestamp field).
    • int_rag_jira__issue_document: title (string field) and created_on (timestamp field).
  • Zendesk
    • int_rag_zendesk__ticket_comment_document: comment_body (string field) and comment_time (timestamp field).
    • int_rag_zendesk__ticket_document: title (string field) and created_on (timestamp field).
• Corrected syntax errors for the default_variable in stg_rag_hubspot__engagement_email and stg_rag_hubspot__engagement_note.
• Updated joins to ensure engagement_deal is the base in the int_rag_hubspot__deal_comment_document CTEs.

Under the Hood

• Updated Hubspot seed files to ensure proper joins on end models.

PR Checklist

Basic Validation

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

• dbt run –full-refresh && dbt test
• [NA] 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:

Was able to reproduce the issue in Snowflake by running the compiled code with a null value that is concatenated and it returning nulls there. Adding the coalesces with the compiled code did produce the full row span expected.

The lone validation test worked too.

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

🪹