[jira] [Commented] (FLINK-18651) implicitly cast the time attribute to regular TIMESTAMP type in regular join

["Jark Wu (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-18651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161738#comment-17161738 ] 

Jark Wu commented on FLINK-18651:
---------------------------------

+1 to do this. 
I think the problem is that we can't change the TIMESTAMP type during optimization. Maybe we need to materialize the time attribute in {{RelTimeIndicatorConverter}}, but this requires large works. 

> implicitly cast the time attribute to regular TIMESTAMP type in regular join
> ----------------------------------------------------------------------------
>
>                 Key: FLINK-18651
>                 URL: https://issues.apache.org/jira/browse/FLINK-18651
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Planner
>            Reporter: godfrey he
>            Priority: Major
>
> Currently, regular join does not accept rowtime attribute field as input, and requires users manually cast the time attribute as regular timestamp. Because time attribute will be out-of-order after regular join, and then we can't do window aggregate based on the time attribute. 
> We can improve it that the planner can implicitly cast the time attribute to regular TIMESTAMP type, and throws exception there is an operator (after join) depended on time attribute, like window aggregate.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)