A fully incremental model, that transforms raw web & mobile event data generated by the Snowplow JavaScript & mobile trackers into a series of derived tables of varying levels of aggregation.
Adding millisecond to mobile integration test case that tests duplicate event_ids with different collector_tstamp. Previously the milliseconds were missing compared to the original mobile package based test events therefore the two events were the same, deduping during base_events_this_run was arbitrary. This should make the test consistent and keep the "true base" row. It turns out when the events are fully duplicated (we test it for web) I had to hardcode the results for Bigquery as well as it seems the row_num is non-deterministic.
Description
Adding millisecond to mobile integration test case that tests duplicate event_ids with different collector_tstamp. Previously the milliseconds were missing compared to the original mobile package based test events therefore the two events were the same, deduping during base_events_this_run was arbitrary. This should make the test consistent and keep the "true base" row. It turns out when the events are fully duplicated (we test it for web) I had to hardcode the results for Bigquery as well as it seems the row_num is non-deterministic.
What type of PR is this? (check all applicable)
Related Tickets & Documents
Checklist
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?