Commit 6e3133c
committed
ctbk update: rebuild rides pyramids (v1/v2/v3) each new month
`update.sh` (unused by ci.yml — legacy) already had normalize/consolidate/
aggregate/spj/sm steps. `ctbk update` (the CLI wired into
`.github/workflows/ci.yml`) mirrored those but omitted the rides-pyramid
rebuild — so /api/rides-{v1,v2,v3} kept serving up-through-prev-month data
while the normalized parquets and aggregates advanced.
Adds `ctbk rides-v1-build -v {v1,v2,v3}` invocations after `spj`, covering
`[prev_month, current]` for all tiers (1h base + 10 derived). Range
includes prev month because start-anchored /1h shards read
`normalized[ym] + normalized[ym+1]` — when prev month was originally
processed, the current month's normalized parquet didn't exist, so
rides that started in prev but ended in current were dropped; rebuilding
the prev-month shard captures them now that the current normalized
parquet exists.
Derived tiers span multi-month (1mo-shard cadences for /3h,/6h,/12h in
v1; broader coverage in v2/v3) or all-time — always overwrite so they
fold in the new data.
Verified via `ctbk update -n -S -W 202606`: emits 3 variants × 11 builds
= 33 invocations targeting `[2026-05, 2026-06]`. Manual backfill for
202605+202606 already run before this commit.1 parent 6eb324f commit 6e3133c
1 file changed
Lines changed: 18 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
60 | 60 | | |
61 | 61 | | |
62 | 62 | | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
63 | 81 | | |
64 | 82 | | |
65 | 83 | | |
| |||
0 commit comments