[Bug] Quotes missing around column names and aliases when hubspot__pass_through_all_columns is enabled

[aryan-wisdom]

Is there an existing issue for this?

• I have searched the existing issues

Describe the issue

The models/stg_hubspot__company.sql, models/stg_hubspot__contact.sql and models/stg_hubspot__deal.sql files are not compiling because quotes are not present around column names when hubspot__pass_through_all_columns is true.

Relevant error log or model output

....

 as company_annual_revenue 
(     
        -- just pass everything through if extra columns are present, but ensure required columns are present.
        property_hs_all-deprecated-85213efe-a820-40c1-815f-4c19fed96ad7 as hs_all-deprecated-85213efe-a820-40c1-815f-4c19fed96ad7,
    from base
)

Expected behavior

....

as company_annual_revenue
(
-- just pass everything through if extra columns are present, but ensure required columns are present.
"property_hs_all-deprecated-85213efe-a820-40c1-815f-4c19fed96ad7" as "hs_all-deprecated-85213efe-a820-40c1-815f-4c19fed96ad7",
from base
)

Possible solution

A for loop around the code:

                fivetran_utils.remove_prefix_from_columns(
                columns=adapter.get_columns_in_relation(ref('stg_hubspot__company_tmp')), 
                prefix='property_', exclude=get_macro_columns(get_company_columns()))

which applies fivetran_utils.quote_column on each column name and alias would help.

dbt Project configurations

vars:
hubspot__pass_through_all_columns: true

Package versions

packages:

• package: fivetran/fivetran_utils
  version: [">=0.4.0", "<0.5.0"]

• package: dbt-labs/spark_utils
  version: [">=0.3.0", "<0.4.0"]

What database are you using dbt with?

redshift

How are you running this dbt package?

dbt Core™

dbt Version

1.7.7

Additional Context

No response

Are you willing to open a PR to help address this issue?

• Yes.
• Yes, but I will need assistance.
• No.

[fivetran-avinash]

Hi @aryan-wisdom , thanks for reporting this issue to us. We were able to reproduce an error locally that when columns were unquoted, the model would not run.

We reconfigured our logic to utilize a new macro that handles quoting columns, and were able to resolve this error so that columns were quoted and the model did compile.

However, we did have to rename the columns so that dashes were now underscores (because that was the source of the problem). Is this acceptable for your data? Just want to check before we proceed forward with this solution.

[aryan-wisdom]

Thanks for taking a look @fivetran-avinash ! That sounds good to me.

[aryan-wisdom]

Any update on this @fivetran-avinash ?

[fivetran-avinash]

Apologies for the delay in responding @aryan-wisdom !

Yes, if you are okay with this approach, we will move this task to accepted and aim to address it in one of the coming sprints.

[aryan-wisdom]

Thanks @fivetran-avinash

[fivetran-joemarkiewicz]

Hi @aryan-wisdom I just wanted to reach out and provide an update that we are planning to address this in the last sprint in the month of October. You can expect us to roll out an update to the HubSpot dbt package then which will address this issue. Thanks for your patience!