You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2016/03/02 14:22:18 UTC

[jira] [Comment Edited] (FLINK-3152) Support all comparisons for Date type

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

Timo Walther edited comment on FLINK-3152 at 3/2/16 1:21 PM:
-------------------------------------------------------------

Hi Dawid,
thanks for your interest. We are currently moving the Table API on top of Apache Calcite (see [FLINK-3221]). The code generation needed to be rewritten for that. This issue is now more complicated than it was before (with the "old" Table API), because the new CodeGenerator does not support the Date type at all yet. We need to sync it with Calcites time/date types first. If you  like to work on this issue anyway I can help you integrating the Date type into the new Table API on Calcite.

Regards,
Timo


was (Author: twalthr):
Hi Dawid,
thanks for your interest. We are currently moving the Table API on top of Apache Calcite (see [FLINK-3221]). The code generation needed to be rewritten for that. This issue is now more complicated than it was before (with the "old" Table API), because the new CodeGenerator does not support the Date type at all. We need to sync it with Calcites time/date types first. If you  like to work on this issue anyway I can help you integrating the Date type into the new Table API on Calcite.

Regards,
Timo

> Support all comparisons for Date type
> -------------------------------------
>
>                 Key: FLINK-3152
>                 URL: https://issues.apache.org/jira/browse/FLINK-3152
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API
>            Reporter: Timo Walther
>
> Currently, the Table API does not support comparisons like "DATE < DATE", "DATE >= DATE". The ExpressionCodeGenerator needs to be adapted for that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)