Session stitching, session_end_tstamp


#1

Hi,
I’m about to create data-modeling for our company and used the example SQL to change it that it fits for our use-case.

I don’t get why at session-stitching, we don’t use the f.session_end_tstamp, because we only do this, because the session went longer than just the timeframe we had, so we have to change every timestamp or event that happend hat the end of this session.

I would change this to f.session_ens_tstamp and f.max_dvce_created_tstamp aswell
https://github.com/snowplow/snowplow/blob/master/5-data-modeling/sql-runner/redshift/sql/web-incremental/05-aggregate/05-01-sessions.sql#L168


#2

Ahh I get it, I was wrong, thought the other way around, it’s okay like this!!