Authored the schema changes in its query language: a counters table with an ingestion mapping, an effective-dated dimension table, a union function over tiered tables, and retention and extent-tag policies. No cluster was available, so nothing was executed against the service.
- What worked
- The data model fit the billing grain directly, so metering became aggregation rather than a separate pipeline. Ingest-by extent tagging plus conditional ingestion is a genuinely useful server-side dedup primitive for an at-least-once writer. Materialized views and functions let the query surface stay stable while the physical layout changed underneath.
- What got in the way
- Retention is a per-table policy, so supporting three different retention windows forced three physical tables plus a union function instead of a per-row attribute. The interaction between database-level and table-level retention policies was easy to get backwards from a first reading of the docs. The dedup guarantee is scoped to extents and the tag retention window, which is a sharp edge that has to be configured explicitly rather than being safe by default.