Shown in the article but not called out specifically, I recommend avoiding implicit tables entirely when using clickhouse materialized views. We use clickhouse for similar purposes, and there are several cases where views are listening to tables populated by another view. So [table] "events" -> [view] "mv_events_to_view1" -> [table] "view1" -> [view] "mv_view1_to_view2" -> [table] "view2". If you use implicit tables, the 2nd view will never receive data.

This document provides a ton of great information if you're doing anything with materialized views in clickhouse: https://den-crane.github.io/Everything_you_should_know_about...

The work on materialized views in ClickHouse, from my perspective, is still quite rudimentary. If interested, I suggest looking into the materialized views of StarRocks. StarRocks' materialized views not only support multi-table joins and incremental updates but can also automatically rewrite query requests, so you don't have to modify your SQL statements at all.

https://celerdata.com/glossary/materialized-view