[ https://issues.apache.org/jira/browse/FLINK-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16907971#comment-16907971 ]
Zhenghua Gao edited comment on FLINK-13651 at 8/16/19 3:40 AM: --------------------------------------------------------------- PlannerExpressionParserImpl of Blink planner does not support char( n )/varchar( n )/decimal(p, s) patterns. was (Author: docete): PlannerExpressionParserImpl of Blink planner does not support char( n )/varchar( n )/decimal(p, s)/timestamp(p) patterns. > Blink planner should parse char(n)/varchar(n)/decimal(p, s) 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)