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

Posted to issues@flink.apache.org by "lamber-ken (JIRA)" <ji...@apache.org> on 2019/05/16 01:28:00 UTC

[jira] [Closed] (FLINK-11010) Flink SQL timestamp is inconsistent with currentProcessingTime()

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

lamber-ken closed FLINK-11010.
------------------------------
    Resolution: Won't Fix

> Flink SQL timestamp is inconsistent with currentProcessingTime()
> ----------------------------------------------------------------
>
>                 Key: FLINK-11010
>                 URL: https://issues.apache.org/jira/browse/FLINK-11010
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / API
>    Affects Versions: 1.6.2, 1.7.0, 1.7.1, 1.8.0
>            Reporter: lamber-ken
>            Assignee: lamber-ken
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Flink SQL timestamp is inconsistent with currentProcessingTime().
>  
> the ProcessingTime is just implemented by invoking System.currentTimeMillis() but the long value will be automatically wrapped to a Timestamp with the following statement: 
> `new java.sql.Timestamp(time - TimeZone.getDefault().getOffset(time));`



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