Why raw connector over materialized views

[ksharinarayanan]

Hi team,

I noticed that meter aggregations were previously done though materialized views, but now it is done by directly executing queries on the raw events table (#1720 and #2420).

#1720 itself says that

Using this connector is expensive to query meters, as will JSON parse each event.

I completely agree to this fact and seems counter intuitive to me, and hence would like to understand what is the rationale behind making this the default?

Thanks

[tothandras]

Materialized views are tricky to maintain and puts pressure on ClickHouse at insert time. MV effectiveness also depends on the permutation of group bys while they make features like Meter edit complicated. We felt MVs serve a small subset of users and we can have better outcomes with query caching even for them instead.
See #2392
But ClickHouse also just released query cache so we are waiting for that testing out before we roll our own.
Entitlements and invoices already have incremental cache similar to this.

[ksharinarayanan]

Makes sense, thanks.