[
https://issues.apache.org/jira/browse/FLINK-12611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847365#comment-16847365
]
Jark Wu edited comment on FLINK-12611 at 5/24/19 9:02 AM:
----------------------------------------------------------
Get it. We don't have a nullable time indicator type.
was (Author: jark):
Get it. We don't have a nullable time indicator type.
However, I think max(rowtime) is a materialize operation, which shouldn't
return a time indicator type but a timestmap. Will that solve the problem?
> Make time indicator nullable in blink
> -------------------------------------
>
> Key: FLINK-12611
> URL: https://issues.apache.org/jira/browse/FLINK-12611
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Reporter: Jingsong Lee
> Assignee: Jingsong Lee
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> SQL: select max(rowtime), count(a) from T
> There will be a AssertionError: type mismatch:
> aggCall type:
> TIMESTAMP(3) NOT NULL
> inferred type:
> TIMESTAMP(3)
> Agg type checking is done before TimeIndicator materializes. So there is a
> exception.
> And before introducing nullable of LogicalType, we should modify this to
> avoid more potential TypeCheck problems.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
