[
https://issues.apache.org/jira/browse/FLINK-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011306#comment-17011306
]
Zhenghua Gao commented on FLINK-13651:
--------------------------------------
[~liyu] [~jark] The root cause is PlannerExpressionParserImpl in both old
planner and blink planner use old type system, and we must keep them as the
same for packaging concern, see
https://issues.apache.org/jira/browse/FLINK-13267
The impact of using new type system for both PlannerExpressionParserImpl needs
to evaluate.
I prefer to postpone it to later release since this only affects Table API.
[~lzljs3620320] Is there any plan to refactor the Scala style Expression
parser?
> 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
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
