materialized_views_ignore_errors
If enabled, exceptions thrown while pushing data to a dependent materialized view (in itsSELECT or in the inner table sink) are logged as a warning and the INSERT statement succeeds. If disabled (default), such an exception propagates and the INSERT statement fails.
This setting controls only error reporting. It does not roll back a write to the source table, and it does not guarantee whether the original block has already been committed to the source table when an error occurs in a dependent view’s pipeline. When disabled (default), the INSERT fails on a view error — retry it with insert deduplication (insert_deduplicate, deduplicate_blocks_in_dependent_materialized_views) for exactly-once delivery to the source table and all dependent views. When enabled, the INSERT reports success despite partial delivery to failing views and their downstream chains; use this only when source-table writes must not be blocked by view-side problems (for example, system.*_log tables). See the CREATE VIEW docs for full semantics.
materialized_views_squash_parallel_inserts
Squash inserts to materialized views destination table of a single INSERT query from parallel inserts to reduce amount of generated parts. If set to false andparallel_view_processing is enabled, INSERT query will generate part in the destination table for each max_insert_thread.