Event Dime
Using native incremental materialized view for model persistence instead for database that support it
- When:
- July 24, 2026 · 2:58 PM
- Where:
- Metabase Discussion
- Source:
- Metabase Discussion
Hi Metabase Team! As titled, I’m curious, is there any technical blocker that makes it hard to do so? Given that most popular data warehouses do support IVM natively, i think that is technically more elegant solution. Freshness is guaranteed by the underlying database, rather than relying on Metabase to manually refreshes the view from scratch after certain period. If it’s technically feasible, would you be open for contribution? I would love to give it a try if it’s not too much. Thanks