parallel-workload: Add iceberg sinks

Cargo.toml

@@ -349,8 +349,8 @@ async-compression = { git = "https://github.com/MaterializeInc/async-compression
 
 # Custom iceberg features for mz
 # All changes should go to the `mz_changes` branch.
-iceberg = { git = "https://github.com/MaterializeInc/iceberg-rust.git", rev = "3e77059b20d3" }
-iceberg-catalog-rest = { git = "https://github.com/MaterializeInc/iceberg-rust.git", rev = "3e77059b20d3" }
+iceberg = { git = "https://github.com/MaterializeInc/iceberg-rust.git", rev = "375a44a45bff" }
+iceberg-catalog-rest = { git = "https://github.com/MaterializeInc/iceberg-rust.git", rev = "375a44a45bff" }
 
 # Custom duckdb crate to support mz needs
 # All changes should go to the `mz_changes` branch.

LICENSE

@@ -13,7 +13,7 @@ Business Source License 1.1
 
 Licensor:                  Materialize, Inc.
 
-Licensed Work:             Materialize Version 20260115
+Licensed Work:             Materialize Version 20260116
                            The Licensed Work is © 2026 Materialize, Inc.
 
 Additional Use Grant:      Within a single installation of the Licensed Work,
@@ -39,7 +39,7 @@ Additional Use Grant:      Within a single installation of the Licensed Work,
                            whose definitions are controlled by such third
                            parties.
 
-Change Date:               January 15, 2030
+Change Date:               January 16, 2030
 
 Change License:            Apache License, Version 2.0
 

doc/user/content/concepts/clusters.md

@@ -92,7 +92,7 @@ The following provides some general guidelines for clusters. See also
 
 ### Three-tier architecture in production
 
-{{% best-practices/architecture/three-tier %}}
+{{% include-from-yaml data="best_practices_details" name="architecture-three-tier" %}}
 
 See also [Operational guidelines](/manage/operational-guidelines/).
 

doc/user/content/concepts/indexes.md

@@ -215,8 +215,8 @@ CREATE INDEX idx_orders_view_qty_price on orders_view (quantity, price);
 
 ### Indexes on views vs. materialized views
 
-{{% views-indexes/table-usage-pattern-intro %}}
-{{% views-indexes/table-usage-pattern %}}
+{{% include-from-yaml data="index_view_details" name="table-usage-pattern-intro" %}}
+{{% include-from-yaml data="index_view_details" name="table-usage-pattern" %}}
 {{% include-md file="shared-content/mat-view-use-cases.md" %}}
 
 ### Indexes and query optimizations
@@ -229,11 +229,11 @@ query performance](/transform-data/optimization/), such as:
 - Provide fast random access for lookup queries (i.e., selecting individual
   keys).
 
-{{% views-indexes/index-query-optimization-specific-instances %}}
+{{% include-from-yaml data="index_view_details" name="index-query-optimization-specific-instances" %}}
 
 ### Best practices
 
-{{% views-indexes/index-best-practices %}}
+{{% include-from-yaml data="index_view_details" name="index-best-practices" %}}
 
 ## Related pages
 

doc/user/content/concepts/views.md

@@ -145,9 +145,9 @@ See also:
 
 ## Indexed views vs. materialized views
 
-{{% views-indexes/table-usage-pattern-intro %}}
+{{% include-from-yaml data="index_view_details" name="table-usage-pattern-intro" %}}
 
-{{% views-indexes/table-usage-pattern %}}
+{{% include-from-yaml data="index_view_details" name="table-usage-pattern" %}}
 
 {{% include-md file="shared-content/mat-view-use-cases.md" %}}
 

doc/user/content/get-started/_index.md

@@ -50,7 +50,7 @@ SQL patterns enabled by streaming like [**Change Data Capture
 filters**](/sql/patterns/temporal-filters/), and
 [**subscriptions**](/sql/subscribe/).
 
-{{% materialize-postgres-compatibility %}}
+{{% include-from-yaml data="materialize_details" name="postgres-compatibility" %}}
 
 ### Real-time data ingestion
 

doc/user/content/get-started/quickstart.md

@@ -559,7 +559,7 @@ views incrementally update the view results. Materialized views persist the
 query results in durable storage and is available across clusters while indexes
 maintain the view results in memory within a single cluster.
 
-{{% views-indexes/table-usage-pattern %}}
+{{% include-from-yaml data="index_view_details" name="table-usage-pattern" %}}
 
 The quickstart used an index since:
 

doc/user/content/ingest-data/_index.md

@@ -146,7 +146,8 @@ guidelines for upsert sources.
 
 ### Scheduling
 
-{{% best-practices/ingest-data/scheduling %}}
+{{% include-from-yaml data="best_practices_details"
+name="ingest-data-scheduling" %}}
 
 ### Dedicate a cluster for the sources
 

doc/user/content/ingest-data/postgres/alloydb.md

@@ -20,7 +20,7 @@ to Materialize using the [PostgreSQL source](/sql/create-source/postgres/).
 
 ## Before you begin
 
-{{% postgres-direct/before-you-begin %}}
+{{% include-from-yaml data="ingest_postgres" name="before-you-begin" %}}
 
 If you don't already have an AlloyDB instance, creating one involves several
 steps, including configuring your cluster and setting up network connections.
@@ -38,7 +38,7 @@ To enable logical replication in AlloyDB, see the
 
 ### 2. Create a publication and a replication user
 
-{{% postgres-direct/create-a-publication-other %}}
+{{% include-from-yaml data="ingest_postgres" name="create-a-publication-other" %}}
 
 ## B. (Optional) Configure network security
 
@@ -187,7 +187,7 @@ scenarios, we recommend separating your workloads into multiple clusters for
 [resource isolation](/sql/create-cluster/#resource-isolation).
 {{< /note >}}
 
-{{% postgres-direct/create-a-cluster %}}
+{{% include-from-yaml data="ingest_postgres" name="create-a-cluster" %}}
 
 ### 2. Create a connection
 
@@ -255,15 +255,15 @@ your networking configuration.
 
 ### 4. Monitor the ingestion status
 
-{{% postgres-direct/check-the-ingestion-status %}}
+{{% include-from-yaml data="ingest_postgres" name="check-the-ingestion-status" %}}
 
 ### 5. Right-size the cluster
 
-{{% postgres-direct/right-size-the-cluster %}}
+{{% include-from-yaml data="ingest_postgres" name="right-size-the-cluster" %}}
 
 ## D. Explore your data
 
-{{% postgres-direct/next-steps %}}
+{{% include-from-yaml data="ingest_postgres" name="next-steps" %}}
 
 ## Considerations
 

doc/user/content/ingest-data/postgres/amazon-aurora.md

@@ -20,7 +20,7 @@ to Materialize using the [PostgreSQL source](/sql/create-source/postgres/).
 
 ## Before you begin
 
-{{% postgres-direct/before-you-begin %}}
+{{% include-from-yaml data="ingest_postgres" name="before-you-begin" %}}
 
 {{< warning >}}
 There is a known issue with Aurora PostgreSQL 16.1 that can cause logical replication to fail with the following error:
@@ -49,7 +49,7 @@ Materialize.
 
 ### 2. Create a publication and a replication user
 
-{{% postgres-direct/create-a-publication-aws %}}
+{{% include-from-yaml data="ingest_postgres" name="create-a-publication-aws" %}}
 
 ## B. (Optional) Configure network security
 
@@ -327,7 +327,7 @@ scenarios, we recommend separating your workloads into multiple clusters for
 {{< /note >}}
 
 
-{{% postgres-direct/create-a-cluster %}}
+{{% include-from-yaml data="ingest_postgres" name="create-a-cluster" %}}
 
 ### 2. Create a connection
 
@@ -435,15 +435,15 @@ your networking configuration.
 
 ### 4. Monitor the ingestion status
 
-{{% postgres-direct/check-the-ingestion-status %}}
+{{% include-from-yaml data="ingest_postgres" name="check-the-ingestion-status" %}}
 
 ### 5. Right-size the cluster
 
-{{% postgres-direct/right-size-the-cluster %}}
+{{% include-from-yaml data="ingest_postgres" name="right-size-the-cluster" %}}
 
 ## D. Explore your data
 
-{{% postgres-direct/next-steps %}}
+{{% include-from-yaml data="ingest_postgres" name="next-steps" %}}
 
 ## Considerations
 

doc/user/content/ingest-data/postgres/amazon-rds.md

@@ -23,7 +23,7 @@ to Materialize using the [PostgreSQL source](/sql/create-source/postgres/).
 
 ## Before you begin
 
-{{% postgres-direct/before-you-begin %}}
+{{% include-from-yaml data="ingest_postgres" name="before-you-begin" %}}
 
 ## A. Configure Amazon RDS
 
@@ -97,7 +97,7 @@ As a first step, you need to make sure logical replication is enabled.
 
 ### 2. Create a publication and a replication user
 
-{{% postgres-direct/create-a-publication-aws %}}
+{{% include-from-yaml data="ingest_postgres" name="create-a-publication-aws" %}}
 
 ## B. (Optional) Configure network security
 
@@ -373,7 +373,7 @@ scenarios, we recommend separating your workloads into multiple clusters for
 [resource isolation](/sql/create-cluster/#resource-isolation).
 {{< /note >}}
 
-{{% postgres-direct/create-a-cluster %}}
+{{% include-from-yaml data="ingest_postgres" name="create-a-cluster" %}}
 
 ### 2. Create a connection
 
@@ -496,15 +496,15 @@ your networking configuration.
 
 ### 4. Monitor the ingestion status
 
-{{% postgres-direct/check-the-ingestion-status %}}
+{{% include-from-yaml data="ingest_postgres" name="check-the-ingestion-status" %}}
 
 ### 5. Right-size the cluster
 
-{{% postgres-direct/right-size-the-cluster %}}
+{{% include-from-yaml data="ingest_postgres" name="right-size-the-cluster" %}}
 
 ## D. Explore your data
 
-{{% postgres-direct/next-steps %}}
+{{% include-from-yaml data="ingest_postgres" name="next-steps" %}}
 
 ## Considerations
 

doc/user/content/ingest-data/postgres/azure-db.md

@@ -20,7 +20,7 @@ to Materialize using the [PostgreSQL source](/sql/create-source/postgres/).
 
 ## Before you begin
 
-{{% postgres-direct/before-you-begin %}}
+{{% include-from-yaml data="ingest_postgres" name="before-you-begin" %}}
 
 ## A. Configure Azure DB
 
@@ -34,7 +34,7 @@ To enable logical replication in Azure DB, see the
 
 ### 2. Create a publication and a replication user
 
-{{% postgres-direct/create-a-publication-other %}}
+{{% include-from-yaml data="ingest_postgres" name="create-a-publication-other" %}}
 
 ## B. (Optional) Configure network security
 
@@ -172,7 +172,7 @@ scenarios, we recommend separating your workloads into multiple clusters for
 [resource isolation](/sql/create-cluster/#resource-isolation).
 {{< /note >}}
 
-{{% postgres-direct/create-a-cluster %}}
+{{% include-from-yaml data="ingest_postgres" name="create-a-cluster" %}}
 
 ### 2. Create a connection
 
@@ -240,15 +240,15 @@ your networking configuration.
 
 ### 4. Monitor the ingestion status
 
-{{% postgres-direct/check-the-ingestion-status %}}
+{{% include-from-yaml data="ingest_postgres" name="check-the-ingestion-status" %}}
 
 ### 5. Right-size the cluster
 
-{{% postgres-direct/right-size-the-cluster %}}
+{{% include-from-yaml data="ingest_postgres" name="right-size-the-cluster" %}}
 
 ## D. Explore your data
 
-{{% postgres-direct/next-steps %}}
+{{% include-from-yaml data="ingest_postgres" name="next-steps" %}}
 
 ## Considerations