Closed stevensnicholas closed 1 month ago
@stevensnicholas Could you clarify what you mean by this?
If events are processed and contain dvce_created_tstamp they will be missing
This logic looks like as long as the dvce_created_tstamp is within the days_late_allowed threshold (when compared to dvce_sent_tstamp) it should be included in the model.
Sorry, that was a poorly worded title - if either dvce_created_tstamp or dvce_sent_tstamp are null those rows will be missing from events this run. Because either side of that where clause will be comparing to null.
Thanks - that makes sense let me raise with the team.
Linking #176 as an update courtesy of the brilliant @agnessnowplow
Closing as this should now be solved with the latest release.
There is the use of dvce_created_tstamp is in a predicate in the macro https://github.com/snowplow/dbt-snowplow-utils/blob/19d16b37c9bbf324a70037859ef608e3fffb004f/macros/base/base_create_snowplow_sessions_lifecycle_manifest.sql#L65 . If events are processed and contain dvce_created_tstamp they will be missing