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
The get_url_parameter() macro breaks on Spark SQL (Databricks). I've come up with a replacement macro that'll work on SparkSQL and am wondering if I could contribute that fix.
installed version: 0.19.1
latest version: 0.19.1
Up to date!
Plugins:
- spark: 0.19.1
Are you interested in contributing the fix?
I'm happy to contribute my macro which works on SparkSQL. If there's a way for dbt_utils to know which database or adapter it's running on, it could pass the appropriate macro?
The text was updated successfully, but these errors were encountered:
@foundinblank I think this could be fixed by the improvements to spark__split_part in spark-utils v0.2.0 (just released last week). Could you try upgrading your version of spark-utils, and see if that works any better?
Describe the bug
The
get_url_parameter()
macro breaks on Spark SQL (Databricks). I've come up with a replacement macro that'll work on SparkSQL and am wondering if I could contribute that fix.Steps to reproduce
This was triggered when setting up Google Ads which uses
get_url_parameter()
macros: https://github.com/fivetran/dbt_google_ads_source/blob/master/models/stg_google_ads__final_url_performance.sql#L30-L34.Expected results
I expected no errors to be thrown and UTM parameters to be parsed out per the model definition.
Actual results
Model fails to build with the error message:
It passes when using this local macro as a replacement (stored in our
/macros
folder) which overwrites dbt_util's macro:System information
packages.yml
Which database are you using dbt with?
The output of
dbt --version
:Are you interested in contributing the fix?
I'm happy to contribute my macro which works on SparkSQL. If there's a way for
dbt_utils
to know which database or adapter it's running on, it could pass the appropriate macro?The text was updated successfully, but these errors were encountered: