RisingWave Community - How do materialized views created by the same table handle updates internally?

Materialized views created from the same table will update when there is an update to the base table, regardless of whether the contents of the view depend on the updated columns.
The optimizer plays a crucial role in determining whether an update to a materialized view is necessary based on the affected columns.
The internal mechanism involves dispatching updates from the upstream table to the downstream materialized views, but optimizations can prevent unnecessary updates.
The ProjectExecutor can detect the necessity of updates to downstream materialized views by analyzing which columns are required in the views.
The discussion also mentions a PR that addresses the issue by optimizing the update dispatch process. More details can be found in the PR: PR Link