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/27 16:08:00 UTC
[jira] [Resolved] (FLINK-39284) CREATE OR ALTER MATERIALIZED TABLE doesn't respect schema of existing table
[ https://issues.apache.org/jira/browse/FLINK-39284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Nuyanzin resolved FLINK-39284.
-------------------------------------
Fix Version/s: 2.3.0
Resolution: Fixed
> CREATE OR ALTER MATERIALIZED TABLE doesn't respect schema of existing table
> ---------------------------------------------------------------------------
>
> Key: FLINK-39284
> URL: https://issues.apache.org/jira/browse/FLINK-39284
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Reporter: Sergey Nuyanzin
> Assignee: Sergey Nuyanzin
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> A number of cases like
> {code:sql}
> CREATE MATERIALIZED TABLE mt1 (
> id INT, t TIMESTAMP_LTZ(3)
> )
> AS SELECT 1 as id, current_timestamp as t
> {code}
> and then
> {code:sql}
> CREATE OR ALTER MATERIALIZED TABLE mt1 (
> id INT, t TIMESTAMP_LTZ(3),
> WATERMARK FOR t as current_timestamp - INTERVAL '5' SECOND
> )
> AS SELECT 1 as id, current_timestamp as t
> {code}
> it will ignore watermark (all cases like create/modify/drop)
> same for constraint
> also similar issue for column comments
--
This message was sent by Atlassian Jira
(v8.20.10#820010)