[jira] [Closed] (FLINK-16270) Use LogicalType to equals/hashcode in TableSchema

["Jingsong Lee (Jira)" <ji...@apache.org>]

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

Jingsong Lee closed FLINK-16270.
--------------------------------
    Resolution: Invalid

> Use LogicalType to equals/hashcode in TableSchema
> -------------------------------------------------
>
>                 Key: FLINK-16270
>                 URL: https://issues.apache.org/jira/browse/FLINK-16270
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / API
>            Reporter: Jingsong Lee
>            Assignee: Jingsong Lee
>            Priority: Major
>             Fix For: 1.11.0
>
>
>  
> {code:java}
> - name: TableNumber2
>     type: source
>     $VAR_UPDATE_MODE
>     schema:
>       - name: IntegerField2
>         type: INT
>       - name: StringField2
>         type: VARCHAR
>       - name: TimestampField3
>         type: TIMESTAMP
>     connector:
>       type: filesystem
>       path: "$VAR_SOURCE_PATH2"
>     format:
>       type: csv
>       fields:
>         - name: IntegerField2
>           type: INT
>         - name: StringField2
>           type: VARCHAR
>         - name: TimestampField3
>           type: TIMESTAMP
>       line-delimiter: "\n"
>       comment-prefix: "#"
> {code}
> Table like this will fail in SQL-CLI.
> The root cause is we will convert the properties into CatalogTableImpl and then convert into properties again. The schema type properties will use new type systems then which is not equal to the legacy types.



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