Concept map: Slowly changing dimensions and backfills
Prerequisites (two levels) and direct dependents of Slowly changing dimensions and backfills. Show everything
- 3prerequisites shown
- 0direct dependents
- 1lessons use it
Taught and used in
Insights 14
- Deduplicate late-arriving corrections by business key and load time, explicitly
- Retire fields in an event or response schema; never reuse a name or number with a new meaning
- Pin pipeline reads to the logical run date so a backfill reproduces history
- Mark recent periods as provisional until late-arriving data has had time to land
- Make every load and backfill idempotent so a rerun cannot double-count
- Join facts to the dimension version that was valid at event time, not to current attributes
- Keep facts whose dimension record has not arrived yet, using an explicit unknown member
- Pick the slowly-changing-dimension type per attribute by asking whether history may change past answers
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