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
Right now, Snowplow models are encoded as macros in order to implement cross-database support. Instead, we should experiment with making models specifically for each support adapter. I think broadly, this falls into:
I don't think we can configure this at a folder level in dbt_project.yml, but it might be worth exploring if there's some clever way to implement that.
The results of this experimentation might result is us wanting to keep the adapter macro pattern, but I'm interested in exploring alternative ways of supporting cross-db model implementations in packages!
The text was updated successfully, but these errors were encountered:
Resolved in #62. Once 0.16.1 comes out, and dbt supports returning boolean YML values from Jinja macros, we can pursue an even-more seamless implementation in dbt_project.yml.
Right now, Snowplow models are encoded as macros in order to implement cross-database support. Instead, we should experiment with making models specifically for each support adapter. I think broadly, this falls into:
The models directory might look like:
Every model would need to have a config like:
I don't think we can configure this at a folder level in
dbt_project.yml
, but it might be worth exploring if there's some clever way to implement that.The results of this experimentation might result is us wanting to keep the adapter macro pattern, but I'm interested in exploring alternative ways of supporting cross-db model implementations in packages!
The text was updated successfully, but these errors were encountered: