You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Leonard Xu (Jira)" <ji...@apache.org> on 2019/12/20 06:21:00 UTC
[jira] [Updated] (FLINK-15334) Fix schemaValidator because
properties mapping may change if user defined generated columns before
custom columns
[ https://issues.apache.org/jira/browse/FLINK-15334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leonard Xu updated FLINK-15334:
-------------------------------
Description:
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.
was:
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" +
will get wrong properties.
> Fix schemaValidator because properties mapping may change if user defined generated columns before custom columns
> -------------------------------------------------------------------------------------------------------------------
>
> 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
> Priority: Major
> Fix For: 1.10.0
>
>
> 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)