Hotfix for problem with new BQ loader with shorter col names

[tv2-tjebsen]

Description & motivation

When we have implemented the new BQ loader that has similar style to other warehouses with cols named like my_schema_1 and not my_schema_1_0_0, the built in logic of normalize broke. This is a simple fix to the problem but should probably be handled better to account for all changes. We have further problems as well but most of these can be fixed with custom scripts etc.

Please chime in with comments or other suggestions. We really like the normalize package

Checklist

• I have verified that these changes work locally
• [N/A] I have updated the README.md (if applicable)
• [N/A] I have added tests & descriptions to my models (and macros if applicable)
• [N/A] I have raised a documentation PR if applicable (Link here if required)

[agnessnowplow]

Hi @tv2-tjebsen, thanks for raising this! We understand the issue and are investigating to come up with a fix on this.

[tv2-tjebsen]

Are there any news on this? We keep hitting cases where this is a problem, as many of our events start with the same prefixes, eg. ..._video_start and ..._video_end that gets values from each other when the different event happens

[agnessnowplow]

Hi @tv2-tjebsen , sorry for the wait, I've checked with the product team and the plan is to add this in for our next sprint which means it should be released in roughly two weeks. In the meantime you could temporarily overwrite it in your dbt project as a macro overwrite with the same name (as it is in a dispatch macro).

[bassrock]

@agnessnowplow is there any update on releasing this?

[agnessnowplow]

Hi @bassrock, apologies for the silence on this, we are working on release v0.4.0 at the moment which will tackle this topic as well. The release is expected within the coming week or two.