You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhenghua Gao (JIRA)" <ji...@apache.org> on 2019/08/15 09:58:00 UTC
[jira] [Updated] (FLINK-13651) Blink planner should parse
char(n)/varchar(n)/decimal(p, s)/timestamp(p) inside a string to
corresponding datatype
[ https://issues.apache.org/jira/browse/FLINK-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhenghua Gao updated FLINK-13651:
---------------------------------
Summary: Blink planner should parse char(n)/varchar(n)/decimal(p, s)/timestamp(p) inside a string to corresponding datatype (was: Blink planner should support parse char(n)/varchar(n)/decimal(p, s)/timestamp(p) inside a string to corresponding datatype)
> Blink planner should parse char(n)/varchar(n)/decimal(p, s)/timestamp(p) inside a string to corresponding datatype
> ------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-13651
> URL: https://issues.apache.org/jira/browse/FLINK-13651
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 1.9.0, 1.10.0
> Reporter: Zhenghua Gao
> Priority: Major
>
> could reproduce in ScalarFunctionsTest:
> `testAllApis(
> 'f31.cast(DataTypes.DECIMAL(38, 18)).truncate(2),
> "f31.cast(DECIMAL(38, 18)).truncate(2)",
> "truncate(cast(f31 as decimal(38, 18)), 2)",
> "-0.12")`
>
> A possible reason is LookupCallResolver treat decimal(38, 18) as a function call.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)