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

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

[table-planner-blink] Add table source and table sink it case using 
varchar/char/decimal precision
 - master: 5b90b16b1d2d4dc48a0edfd12844ab1ada871586
 - 1.9: 78267df626bd8fb04aa4d7204d07ed28b34d53ee
 
[table-planner-blink] source/sink code should use planner type conversion to 
keep precision
 - master: e2a8b95e4703e77a963cee5641bffe2e5b8a6f49
 - 1.9: 1d2f96e9ac2ec2c5436232ea83d8bb4ca7184a36
 
[table-planner-blink] Introduce isAssignable to use soft check in 
TableSourceUtil
 - master: 9dddae827e3f117b3527254701119c10909a3ac5
 - 1.9: 54eacb62ad4d1eeb583dde4012420db9c581b650
 
[table-planner-blink] Deal with InputFormatTableSource in planner to use 
planner type convertion to keep precision
 - master: ebf18db29b9b8480459e20b307e07980657e75e5
 - 1.9: a58817b348ec4242ccb3b92cce29099f6d56af13
 
[table-api] Use DataType in ConnectorCatalogTable instead of TypeInformation
 - master: 49202e2cf849dce7df3856ec9f40b1b5596a7ae9
 - 1.9: 29e350efcf4ba453617e6091368751b0739ab2dc
 

> blink-planner should support decimal precision to table source
> --------------------------------------------------------------
>
>                 Key: FLINK-13495
>                 URL: https://issues.apache.org/jira/browse/FLINK-13495
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Planner
>            Reporter: Jingsong Lee
>            Assignee: Jingsong Lee
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Now there is an exception when use DataTypes.DECIMAL(5, 2) to table source 
> when use blink-planner.
> Some conversions between DataType and TypeInfo loose precision information.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to