From e105fc80360641b1663efd7af12be094e0394421 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 20 Jul 2026 15:56:31 +0000 Subject: [PATCH 1/4] v26.34.0 draft release notes Co-Authored-By: Claude Opus 4.6 --- doc/user/content/releases/_index.md | 37 +++++++++++++++++++ .../self_managed_operator_compatibility.yml | 5 +++ 2 files changed, 42 insertions(+) diff --git a/doc/user/content/releases/_index.md b/doc/user/content/releases/_index.md index ba070a8aea703..c197eeb3037b8 100644 --- a/doc/user/content/releases/_index.md +++ b/doc/user/content/releases/_index.md @@ -15,6 +15,43 @@ Starting with the v26.1.0 release, Materialize releases on a weekly schedule for both Cloud and Self-Managed. See [Release schedule](/releases/schedule) for details. {{}} +## v26.34.0 +*Released to Materialize Cloud: 2026-07-23*
+*Released to Materialize Self-Managed: 2026-07-24*
+ +### Background cluster reconfiguration {#v26.34-background-cluster-reconfiguration} +The cluster controller is now enabled by default. `ALTER CLUSTER` for configuration changes (such as resizing) now returns immediately and converges in the background, rather than blocking until the new replica set is ready. `CREATE CLUSTER` and `ALTER CLUSTER` also accept the new `AUTO SCALING STRATEGY` option for configuring hydration-burst autoscaling behavior. + +### Improvements {#v26.34-improvements} +- **Azure SQL source support**: Materialize can now ingest data from Azure SQL databases using the SQL Server source connector. +- **AWS Glue Schema Registry for sinks**: `CREATE SINK` now supports AWS Glue Schema Registry for Avro-encoded Kafka sinks, as an alternative to Confluent Schema Registry. +- **Configurable Iceberg sink commit interval**: The commit interval of an existing Iceberg sink can now be altered using `ALTER ... SET COMMIT INTERVAL`, with a minimum of 1 second. +- **MCP query tool replica routing**: The MCP developer query tool now accepts a `cluster_replica` parameter, enabling `EXPLAIN ANALYZE` on clusters with more than one replica. +- **Smaller container images**: The `environmentd` and `clusterd` container images now use a distroless base, reducing image size and attack surface for Self-Managed deployments. + +### Agent Skills {#v26.34-agent-skills} +- **Materialize Terraform Provider**: New agent skill covering Terraform provider configuration for Cloud and self-managed deployments, resource conventions, cross-resource patterns, import workflows, and known gotchas. +- **Materialize Terraform Self-Managed**: New agent skill covering the Terraform modules for deploying self-managed Materialize on AWS, Azure, and GCP, including IAM-based storage auth, upgrade procedures, and project integration patterns. + +### Bug Fixes {#v26.34-bug-fixes} +- Fixed a critical bug where a pending replacement materialized view could destroy the data of its live target materialized view after an environmentd restart, by advancing the shared persist shard's since to the empty frontier. +- Fixed a correctness bug in join processing where incoming batches could be silently dropped after trace compaction, causing lost updates without error. +- Fixed multiple soundness bugs in persist filter pushdown that could silently drop matching rows or cause `persist filter pushdown correctness violation` panics. +- Fixed a bug in multi-statement read transactions where a timestamp-independent first statement (e.g., a query over a constant-folded view) could cause subsequent statements to read from incorrect time domains, resulting in errors or incorrect results. +- Fixed `ALTER MATERIALIZED VIEW ... APPLY REPLACEMENT` crashing the coordinator when a temporary view or index depended on the target materialized view. +- Fixed non-temporary objects (views, indexes, etc.) being allowed to depend on temporary objects, which could lead to dangling references when the session ended. +- Fixed stack overflow crashes in the adapter when processing environments with deeply nested object dependencies. +- Fixed a stack overflow when comparing deeply nested values (e.g., deeply nested JSONB) in query result ordering. +- Fixed a stack overflow when executing read-then-write statements (e.g., `INSERT INTO ... SELECT`) over deeply chained view hierarchies. +- Fixed stack overflow or memory exhaustion when resolving pathologically deep or wide custom types. +- Fixed a crash on diskless replicas where restarting upsert sources could encounter stale RocksDB state. +- Fixed environmentd crash-looping on startup when a tombstoned persist shard was still referenced in the catalog. +- Fixed `SET TRANSACTION ... READ WRITE` silently modifying session state before returning an error. +- `CREATE ROLE` now rejects the reserved role specification names `current_user`, `current_role`, `session_user`, `user`, and `none`. +- Fixed a user-created schema named `information_schema` bypassing the `mz_catalog_server` cluster restriction, allowing user queries to run on a reserved system cluster. +- Fixed `kubectl apply --server-side` failing for Materialize v1 CRDs when managed fields were originally recorded at v1alpha1, blocking GitOps tooling in Self-Managed deployments. +- Fixed the Self-Managed Console deriving the MCP server URL from the pgwire hostname instead of the HTTP endpoint, causing MCP connections to fail when pgwire and HTTP are served on separate hostnames. + ## v26.33.0 *Released to Materialize Cloud: 2026-07-16*
*Released to Materialize Self-Managed: 2026-07-17*
diff --git a/doc/user/data/self_managed/self_managed_operator_compatibility.yml b/doc/user/data/self_managed/self_managed_operator_compatibility.yml index 23c04b0a431fc..332ef5781e7c5 100644 --- a/doc/user/data/self_managed/self_managed_operator_compatibility.yml +++ b/doc/user/data/self_managed/self_managed_operator_compatibility.yml @@ -5,6 +5,11 @@ columns: - column: Release date - column: Notes rows: + - Materialize Operator: v26.34 + orchestratord version: v26.34 + environmentd version: v26.34 + Release date: "2026-07-24" + Notes: "See [v26.34 release notes](/releases/#v26340)" - Materialize Operator: v26.33 orchestratord version: v26.33 environmentd version: v26.33 From d2a0907f5fae0eafeb689bad7d4559f1fcd3ec0e Mon Sep 17 00:00:00 2001 From: Jon Currey Date: Mon, 20 Jul 2026 12:58:57 -0400 Subject: [PATCH 2/4] v26.34.0 release notes: set real release dates (2026-07-21) Release to Materialize Cloud and Self-Managed on 2026-07-21. Replaces the provisional weekly-cadence dates from the rc.1 draft. Co-Authored-By: Claude Opus 4.8 --- doc/user/content/releases/_index.md | 4 ++-- .../data/self_managed/self_managed_operator_compatibility.yml | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/user/content/releases/_index.md b/doc/user/content/releases/_index.md index c197eeb3037b8..caa23cc0fafcb 100644 --- a/doc/user/content/releases/_index.md +++ b/doc/user/content/releases/_index.md @@ -16,8 +16,8 @@ both Cloud and Self-Managed. See [Release schedule](/releases/schedule) for deta {{}} ## v26.34.0 -*Released to Materialize Cloud: 2026-07-23*
-*Released to Materialize Self-Managed: 2026-07-24*
+*Released to Materialize Cloud: 2026-07-21*
+*Released to Materialize Self-Managed: 2026-07-21*
### Background cluster reconfiguration {#v26.34-background-cluster-reconfiguration} The cluster controller is now enabled by default. `ALTER CLUSTER` for configuration changes (such as resizing) now returns immediately and converges in the background, rather than blocking until the new replica set is ready. `CREATE CLUSTER` and `ALTER CLUSTER` also accept the new `AUTO SCALING STRATEGY` option for configuring hydration-burst autoscaling behavior. diff --git a/doc/user/data/self_managed/self_managed_operator_compatibility.yml b/doc/user/data/self_managed/self_managed_operator_compatibility.yml index 332ef5781e7c5..f94bebb86a0f0 100644 --- a/doc/user/data/self_managed/self_managed_operator_compatibility.yml +++ b/doc/user/data/self_managed/self_managed_operator_compatibility.yml @@ -8,7 +8,7 @@ rows: - Materialize Operator: v26.34 orchestratord version: v26.34 environmentd version: v26.34 - Release date: "2026-07-24" + Release date: "2026-07-21" Notes: "See [v26.34 release notes](/releases/#v26340)" - Materialize Operator: v26.33 orchestratord version: v26.33 From 8ca71ac355f5af004cab2fa0b922bbf292b85a01 Mon Sep 17 00:00:00 2001 From: Jon Currey Date: Mon, 20 Jul 2026 13:02:22 -0400 Subject: [PATCH 3/4] v26.34.0 release notes: drop AWS Glue Schema Registry entry The Glue Schema Registry sink (#37618) is gated behind the enable_glue_schema_registry feature flag, which is off by default at the v26.34.0 tag, so the capability is not reachable by customers in this release. Remove the entry to avoid advertising an unavailable feature. Co-Authored-By: Claude Opus 4.8 --- doc/user/content/releases/_index.md | 1 - 1 file changed, 1 deletion(-) diff --git a/doc/user/content/releases/_index.md b/doc/user/content/releases/_index.md index caa23cc0fafcb..4164e5a274148 100644 --- a/doc/user/content/releases/_index.md +++ b/doc/user/content/releases/_index.md @@ -24,7 +24,6 @@ The cluster controller is now enabled by default. `ALTER CLUSTER` for configurat ### Improvements {#v26.34-improvements} - **Azure SQL source support**: Materialize can now ingest data from Azure SQL databases using the SQL Server source connector. -- **AWS Glue Schema Registry for sinks**: `CREATE SINK` now supports AWS Glue Schema Registry for Avro-encoded Kafka sinks, as an alternative to Confluent Schema Registry. - **Configurable Iceberg sink commit interval**: The commit interval of an existing Iceberg sink can now be altered using `ALTER ... SET COMMIT INTERVAL`, with a minimum of 1 second. - **MCP query tool replica routing**: The MCP developer query tool now accepts a `cluster_replica` parameter, enabling `EXPLAIN ANALYZE` on clusters with more than one replica. - **Smaller container images**: The `environmentd` and `clusterd` container images now use a distroless base, reducing image size and attack surface for Self-Managed deployments. From 2a77350e2c9cd03dc7a75c6ae61e8dd203dac64f Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 20 Jul 2026 20:20:06 +0000 Subject: [PATCH 4/4] Add release note for AWS Glue Schema Registry support for sinks (Cloud only) --- doc/user/content/releases/_index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/user/content/releases/_index.md b/doc/user/content/releases/_index.md index 4164e5a274148..e7cece884c7cf 100644 --- a/doc/user/content/releases/_index.md +++ b/doc/user/content/releases/_index.md @@ -22,6 +22,9 @@ both Cloud and Self-Managed. See [Release schedule](/releases/schedule) for deta ### Background cluster reconfiguration {#v26.34-background-cluster-reconfiguration} The cluster controller is now enabled by default. `ALTER CLUSTER` for configuration changes (such as resizing) now returns immediately and converges in the background, rather than blocking until the new replica set is ready. `CREATE CLUSTER` and `ALTER CLUSTER` also accept the new `AUTO SCALING STRATEGY` option for configuring hydration-burst autoscaling behavior. +### AWS Glue Schema Registry Support for Sinks {#v26.34-aws-glue-schema-registry-support-sinks} +Kafka sinks can now use AWS Glue Schema Registry for Avro schema management via the new `FORMAT AVRO USING AWS GLUE SCHEMA REGISTRY` syntax on `CREATE SINK`, as an alternative to the Confluent Schema Registry. This is currently available on Materialize Cloud only. + ### Improvements {#v26.34-improvements} - **Azure SQL source support**: Materialize can now ingest data from Azure SQL databases using the SQL Server source connector. - **Configurable Iceberg sink commit interval**: The commit interval of an existing Iceberg sink can now be altered using `ALTER ... SET COMMIT INTERVAL`, with a minimum of 1 second.