You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Sergey Nuyanzin (Jira)" <ji...@apache.org> on 2026/03/20 20:04:00 UTC
[jira] [Commented] (FLINK-39279) CREATE OR ALTER MATERIALIZED TABLE doesn't respect distribution change
[ https://issues.apache.org/jira/browse/FLINK-39279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18067176#comment-18067176 ]
Sergey Nuyanzin commented on FLINK-39279:
-----------------------------------------
Merged as [e6ac376f362d37015585f5d7f00b4c754c28d071|https://github.com/apache/flink/commit/e6ac376f362d37015585f5d7f00b4c754c28d071]
> CREATE OR ALTER MATERIALIZED TABLE doesn't respect distribution change
> ----------------------------------------------------------------------
>
> Key: FLINK-39279
> URL: https://issues.apache.org/jira/browse/FLINK-39279
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Reporter: Sergey Nuyanzin
> Assignee: Sergey Nuyanzin
> Priority: Major
> Labels: pull-request-available
>
> In case there is existing materialized table like
> {code:sql}
> CREATE MATERIALIZED TABLE mt (
> DISTRIBUTED BY HASH (b) INTO 7 BUCKETS
> AS SELECT t1.* FROM t1
> {code}
> and then if there is a query like (with different or absent distribution)
> {code:sql}
> CREATE OR ALTER MATERIALIZED TABLE mt (
> DISTRIBUTED BY HASH (z) INTO 123 BUCKETS
> AS SELECT t1.* FROM t1
> {code}
> another example when first materialized table is without distribution and in the second with.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)