flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-11010) Flink SQL timestamp is inconsistent with currentProcessingTime()
Date Wed, 12 Dec 2018 03:57:00 GMT

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

ASF GitHub Bot commented on FLINK-11010:

samsai edited a comment on issue #7180: [FLINK-11010] [TABLE] Flink SQL timestamp is inconsistent
with currentProcessingTime()
URL: https://github.com/apache/flink/pull/7180#issuecomment-446445016
   @walterddr could you please check the timezone problem when dealing with eventtime?  
   it seems that lamber-ken's commit only fixed proc time.  
   Would you please refer to my previous comment to take a look at my eventtime usecase. thanks
a lot!
   i found the correct timestamp was changed in OutputRowtimeProcessFunction, using SqlFunctions.internalToTimestamp(),
i'm not sure whether its redundant or not.  
   please fix this problem. thx

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> 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 API &amp; SQL
>    Affects Versions: 1.6.2, 1.7.0, 1.8.0, 1.7.1
>            Reporter: lamber-ken
>            Assignee: lamber-ken
>            Priority: Major
>              Labels: pull-request-available
> 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

View raw message