lamber-ken opened a new pull request #7180: [FLINK-11010] [TABLE] Flink SQL 
timestamp is inconsistent with currentProcessingTime()
URL: https://github.com/apache/flink/pull/7180
 
 
   ## What is the purpose of the change
   
   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));`
   
   
   ## Brief change log
   
     `org.apache.flink.table.codegen.CodeGenerator#generateProctimeTimestamp` 
      add Default TimeZone#offset
   
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (no)
   

----------------------------------------------------------------
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

Reply via email to