snuyanzin opened a new pull request, #22775:
URL: https://github.com/apache/flink/pull/22775

   ## What is the purpose of the change
   
   The PR makes support of `TIME` precision (0-3 - currently only this range, 
I'm going to submit support for micros and nanos in the next PR) including 
casts, time related functions (`CEIL`, `FLOOR`, `OVERLAPS`, agg `MAX`,  `MIN`,  
`LEAD`, `LAG`, singlevalue )
   Also added support of `TIME` precision in csv, json, avro, some tests in 
Kafka (they use agg `MAX` e.g.)
   
   ## Brief change log
   
   *(for example:)*
     - *The TaskInfo is stored in the blob store on job creation time as a 
persistent artifact*
     - *Deployments RPC transmits only the blob storage reference*
     - *TaskManagers retrieve the TaskInfo from the blob cache*
   
   
   ## Verifying this change
   
   A number of tests in table-planner, avro, csv, json, kafka dealing with 
`TIME`
   
   especially 
`flink-table/flink-table-planner/src/test/java/org/apache/flink/table/planner/functions/CastFunctionITCase.java`
 and 
`flink-table/flink-table-planner/src/test/java/org/apache/flink/table/planner/functions/casting/CastRulesTest.java`
   checking different variations of casts to and from `TIME`
   
   
   ## 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, Kubernetes/Yarn, 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? (not applicable )
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to