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
It looks like Snowplow has switched to the new of processing raw data https://github.com/snowplow/data-models and call new data model as V1. Current implementation of DBT module does not suits it anymore. New data model should be supported/adopted by DBT snowplow module.
Describe alternatives you've considered
Possible workaround - create by DBT module all snowplow tables by parsing JSON fields in EVENTS table. E.g. create table com_snowplowanalytics_snowplow_web_page_1 by parsing field EVENTS.contexts_com_snowplowanalytics_snowplow_web_page_1
Who will this benefit?
All users who has using DBT and Snwoplow at the same time on their projects.
The text was updated successfully, but these errors were encountered:
@jtcohen6@drewbanin I'd like to get your insights regarding what is the best way to implement workaround? I have implemented workaround models to new snowflake data model and going to do PR. However, the main question how to configure such switch in logic. I see two options:
Introduce some special variable (quite easy to implement, but not so clear for user what is it).
Just reuse variables like 'snowplow:context:web_page': e.g. value of 'snowplow:events' (atomic.events) = 'snowplow:context:web_page', looks like that we are using snowflake layout with single table and start using workaround solution. (more clear for user, but could be fragile).
Describe the feature
It looks like Snowplow has switched to the new of processing raw data https://github.com/snowplow/data-models and call new data model as V1. Current implementation of DBT module does not suits it anymore. New data model should be supported/adopted by DBT snowplow module.
Describe alternatives you've considered
Possible workaround - create by DBT module all snowplow tables by parsing JSON fields in EVENTS table. E.g. create table com_snowplowanalytics_snowplow_web_page_1 by parsing field EVENTS.contexts_com_snowplowanalytics_snowplow_web_page_1
Who will this benefit?
All users who has using DBT and Snwoplow at the same time on their projects.
The text was updated successfully, but these errors were encountered: