[
https://issues.apache.org/jira/browse/FLINK-11010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706058#comment-16706058
]
ASF GitHub Bot commented on FLINK-11010:
----------------------------------------
lamber-ken commented on issue #7180: [FLINK-11010] [TABLE] Flink SQL timestamp
is inconsistent with currentProcessingTime()
URL: https://github.com/apache/flink/pull/7180#issuecomment-443472946
Thanks for review @walterdd. Yes, Ok, I'm very glad to.
read more about [Calcite
SqlFunctions#internalToTime](https://github.com/apache/calcite/blob/1d2929105f47b944c65529fe59b3072cce167116/core/src/main/java/org/apache/calcite/runtime/SqlFunctions.java#L1751).
and if I give it an event time with unix timestamp 0, then I got the
Timestamp(-28800000). I am confused why `internalToTimestamp` need to subtract
the offset?
----------------------------------------------------------------
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:
[email protected]
> 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 & SQL
> Affects Versions: 1.6.2
> 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
(v7.6.3#76005)
