You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/22 08:14:00 UTC

[jira] [Updated] (FLINK-8045) Add Internal DATE/TIME/TIMESTAMP as internal representation of DATE/TIME/TIMESTAMP

     [ https://issues.apache.org/jira/browse/FLINK-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-8045:
----------------------------------
    Labels: pull-request-available  (was: )

> Add Internal DATE/TIME/TIMESTAMP as internal representation of DATE/TIME/TIMESTAMP
> ----------------------------------------------------------------------------------
>
>                 Key: FLINK-8045
>                 URL: https://issues.apache.org/jira/browse/FLINK-8045
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API &amp; SQL
>            Reporter: Zhenghua Gao
>            Assignee: Zhenghua Gao
>            Priority: Major
>              Labels: pull-request-available
>
> Currently DATE/TIME/TIMESTAMP have internal representation. Such as Date is represented as Int internal. 
> This feature may improve performance processing DATE/TIME/TIMESTAMP data. 
> But I found there is a LIMITATION: internal representation exists only within one operator. 
> We transfer DATE/TIME/TIMESTAMP objects between operators.
> I think we could treat DATE/TIME/TIMESTAMP as internal representation in the whole job, and cast them to java.sql.* as needed(UDF/UDTF/OUTPUT)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)