You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Shuo Cheng (Jira)" <ji...@apache.org> on 2020/03/13 02:36:00 UTC
[jira] [Commented] (FLINK-16577) Exception will be thrown when
computing columnInterval relmetadata in some case
[ https://issues.apache.org/jira/browse/FLINK-16577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058365#comment-17058365 ]
Shuo Cheng commented on FLINK-16577:
------------------------------------
cc [~godfreyhe], [~jark]
> Exception will be thrown when computing columnInterval relmetadata in some case
> -------------------------------------------------------------------------------
>
> Key: FLINK-16577
> URL: https://issues.apache.org/jira/browse/FLINK-16577
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 1.10.0
> Reporter: Shuo Cheng
> Priority: Major
> Fix For: 1.11.0
>
> Attachments: image-2020-03-13-10-32-35-375.png
>
>
> Consider the following SQL
>
> {code:java}
> // a: INT, c: LONG
> SELECT
> c, SUM(a)
> FROM T
> WHERE a > 0.1 AND a < 1
> GROUP BY c{code}
>
> Here the sql type of 0.1 is Decimal and 1 is Integer, and they are both in NUMERIC type family, and do not trigger type coercion, so the plan is:
> {code:java}
> FlinkLogicalAggregate(group=[{0}], EXPR$1=[SUM($1)])
> +- FlinkLogicalCalc(select=[c, a], where=[AND(>(a, 0.1:DECIMAL(2, 1)), <(a, 1))])
> +- FlinkLogicalTableSourceScan(table=[[...]], fields=[a, b, c])
> {code}
> When we calculate the filtered column interval of calc, it'll lead to validation exception of `FiniteValueInterval`:
> !image-2020-03-13-10-32-35-375.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)