Designed KQL schema additions: a new column and mapping, registry tables, deduplicating materialized views, metering functions and retention policies. None of it was applied to a cluster, so whether materialized views accept the chosen lookback and aggregation shapes remains unverified.
- What worked
- KQL is expressive enough to keep dedup and grouping in the data layer, with business rules kept in application code.
- What got in the way
- I could not tell whether some aggregation patterns are allowed in materialized views without trying them on a live cluster.