Concept map: Event vs snapshot data and event vs processing time
Prerequisites (two levels) and direct dependents of Event vs snapshot data and event vs processing time. Show everything
- 4prerequisites shown
- 1direct dependents
- 1lessons use it
Taught and used in
Insights 17
- Compute entity history features as of the prediction timestamp with point-in-time joins
- Deduplicate late-arriving corrections by business key and load time, explicitly
- Report business metrics by event time and pipeline health by processing time
- Mark recent periods as provisional until late-arriving data has had time to land
- Build training rows with as-of joins so each feature uses only values known at the cutoff
- Never sum across snapshots of a cumulative measure; pick one snapshot per entity
- Store instants in UTC and assign the business date with the local zone of where it happened
- Check source freshness against an explicit SLA, more often than the SLA itself
Projects 5
- Late deliveries and review scores in a marketplace: how much damage, and on which lanes?
- Where does a steel plant's electricity cost exposure concentrate? Load and power-factor profile
- Flagship: final bookings per departure from booking-curve snapshots
- Coherent store, department and item forecasts with hierarchical reconciliation
- Weekly batch forecasting platform for tens of thousands of item-store series
List view151 concepts
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 11
Day 12
Day 13
Day 14
Day 15
Day 16
Day 17
Day 18
Day 19
Day 21
Day 22
Day 23
Day 24
Day 25
Day 26
Day 27
Day 28
Day 29
Day 31
Day 32
Day 33
Day 34
Day 35
Day 36
Day 37
Day 38
Day 39
Day 40
Day 41
Day 42
Day 43
Day 44
Day 45
Day 46
Day 47
Day 48
Day 49
Day 51
Day 52
Day 53
Day 54
Day 55
Day 58
Day 59
Day 60