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

Martijn Visser updated FLINK-40798:
-----------------------------------
    Release Note: In an INSERT INTO with a column list or static partitions, an 
ordinal in ORDER BY now refers to the query's select list instead of the sink's 
column order. The plan of such a statement can change, so a stateful job 
without a compiled plan might not restore from an older savepoint.

> Move partial INSERT off the source rewrite in PreValidateReWriter
> -----------------------------------------------------------------
>
>                 Key: FLINK-40798
>                 URL: https://issues.apache.org/jira/browse/FLINK-40798
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Planner
>            Reporter: Martijn Visser
>            Assignee: Martijn Visser
>            Priority: Major
>              Labels: pull-request-available
>
> FLINK-40039 moved CTAS and RTAS off the source rewrite in 
> {{PreValidateReWriter}}. We should do the same for INSERT INTO with a column 
> list or static partitions, which ran into the same problem in FLINK-40694: 
> apply the reordering, NULL padding and static partition values as a 
> projection on the converted plan, keep only the partition and column list 
> checks in {{PreValidateReWriter}} and remove {{SqlRewriterUtils}}.
> As a side effect, an ordinal in ORDER BY then refers to the query's select 
> list instead of the sink's column order.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to