You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Yubin Li (Jira)" <ji...@apache.org> on 2022/11/18 03:11:00 UTC

[jira] [Closed] (FLINK-29929) Correct conversions from ResolvedSchema to TableSchema

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

Yubin Li closed FLINK-29929.
----------------------------
    Resolution: Won't Fix

> Correct conversions from ResolvedSchema to TableSchema
> ------------------------------------------------------
>
>                 Key: FLINK-29929
>                 URL: https://issues.apache.org/jira/browse/FLINK-29929
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / Planner
>            Reporter: Yubin Li
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: image-2022-11-08-19-32-05-894.png
>
>
> In the new schema framework, DataType in Column indicate wether the column is a time attribute and the old api not, we can see that ```DefaultSchemaResolver.resolve()``` include above logic. but in TableSchema.fromResolvedSchema(), we can't see the time attribute removal logic, thus cause a wrong Timestamp DataType. the test case has been in the pull request.
> !image-2022-11-08-19-32-05-894.png!



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