[jira] [Resolved] (FLINK-15334) Fix physcial schema mapping in TableFormatFactoryBase to support define orderless computed column

["Jark Wu (Jira)" <ji...@apache.org>]

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

Jark Wu resolved FLINK-15334.
-----------------------------
    Resolution: Fixed

1.11.0: 898064f4a743b3e10af1c6d7a0d4d73c432815f4
1.10.0: a1fe7adfd1f7b1807d611614ae88838bb178023f

> Fix physcial schema mapping in TableFormatFactoryBase to support define orderless computed column 
> --------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-15334
>                 URL: https://issues.apache.org/jira/browse/FLINK-15334
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / API
>    Affects Versions: 1.10.0
>            Reporter: Leonard Xu
>            Assignee: Leonard Xu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> If user defined a DDL like:
> "CREATE TABLE orders (\n" +
>             "  order_id STRING,\n" +
>             "  item    STRING,\n" +
>             "  currency STRING,\n" +
>             "  amount INT,\n" +
>             "  amount_kg as amount * 1000,\n" +
>             "  order_time TIMESTAMP(3),\n" +
>             "  ts as order_time + INTERVAL '1' SECOND,\n" +
>             "  WATERMARK FOR ts AS ts\n" +
>             ") WITH (\n" +
> which generated columns(eg:amount_kg) defined before custom columns(eg:order_time) will get wrong properties. 
> in this case, we still use index 5 for column order_time and the new index should be 4  after prune generated column.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)