[GitHub] walterddr commented on issue #7180: [FLINK-11010] [TABLE] Flink SQL timestamp is inconsistent with currentProcessingTime()

2018-12-11 Thread GitBox
walterddr commented on issue #7180: [FLINK-11010] [TABLE] Flink SQL timestamp 
is inconsistent with currentProcessingTime()
URL: https://github.com/apache/flink/pull/7180#issuecomment-446457485
 
 
   > @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!
   > --update
   > 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
   
   FLINK-11010 only reports bugs for utilizing `currentProcessingTime()`. maybe 
we can mark the JIRA as duplicate of FLINK-8353 and focus on addressing the 
bigger overall timezone problem instead. what do you think?


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] walterddr commented on issue #7180: [FLINK-11010] [TABLE] Flink SQL timestamp is inconsistent with currentProcessingTime()

2018-12-06 Thread GitBox
walterddr commented on issue #7180: [FLINK-11010] [TABLE] Flink SQL timestamp 
is inconsistent with currentProcessingTime()
URL: https://github.com/apache/flink/pull/7180#issuecomment-445103065
 
 
   Hi @lamber-ken sorry for the late response. I am a bit confuse with the JIRA 
ticket description and the PR comments. 
   
   I am under the impression that the goal should make all internal times 
GMT-based regardless of where the code runs. Thus `currentProcessingTime()` 
should return a GMT-based time. if my understanding is correct, shouldn't the 
fix be in the "timerService" side instead?


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] walterddr commented on issue #7180: [FLINK-11010] [TABLE] Flink SQL timestamp is inconsistent with currentProcessingTime()

2018-12-02 Thread GitBox
walterddr commented on issue #7180: [FLINK-11010] [TABLE] Flink SQL timestamp 
is inconsistent with currentProcessingTime()
URL: https://github.com/apache/flink/pull/7180#issuecomment-443522584
 
 
   Hi @lamber-ken . the minimum reproduction result should be a good starting 
point for adding test/ITCase to justify your change. I also commented on the 
JIRA ticket as well. 


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:
us...@infra.apache.org


With regards,
Apache Git Services