[ 
https://issues.apache.org/jira/browse/FLINK-39077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Nuyanzin updated FLINK-39077:
------------------------------------
    Description: 
For instance if there is initial MT as 
{code:sql}
CREATE MATERIALIZED TABLE mt (id INT, metadata1 METADATA INT VIRTUAL, metadata2 
METADATA INT VIRTUAL) AS SELECT 1 id;
{code}
and then
{code:sql}
ALTER MATERIALIZED TABLE mt AS SELECT 1 AS id, 'name' AS name;
{code}


Update: finally it was decided to not support changing of query for such cases 
because it is not clear what is is intention of users regarding non persisted 
column position in such case
Instead users can use either CREATE OR ALTER

  was:
For instance if there is initial MT as 
{code:sql}
CREATE MATERIALIZED TABLE mt (id INT, metadata1 METADATA INT VIRTUAL, metadata2 
METADATA INT VIRTUAL) AS SELECT 1 id;
{code}
and then
{code:sql}
ALTER MATERIALIZED TABLE mt AS SELECT 1 AS id, 'name' AS name;
{code}


Update: finally it was decided to not support changing of query for such cases
Instead users can use either CREATE OR ALTER


> Calculation of table changes for MT with several non persisted columns might 
> fail
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-39077
>                 URL: https://issues.apache.org/jira/browse/FLINK-39077
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Sergey Nuyanzin
>            Assignee: Sergey Nuyanzin
>            Priority: Major
>              Labels: pull-request-available
>
> For instance if there is initial MT as 
> {code:sql}
> CREATE MATERIALIZED TABLE mt (id INT, metadata1 METADATA INT VIRTUAL, 
> metadata2 METADATA INT VIRTUAL) AS SELECT 1 id;
> {code}
> and then
> {code:sql}
> ALTER MATERIALIZED TABLE mt AS SELECT 1 AS id, 'name' AS name;
> {code}
> Update: finally it was decided to not support changing of query for such 
> cases because it is not clear what is is intention of users regarding non 
> persisted column position in such case
> Instead users can use either CREATE OR ALTER



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to