danny0405 opened a new pull request #11340: [Flink 14338] Upgrade Calcite 
version to 1.22 for Flink SQL
URL: https://github.com/apache/flink/pull/11340
 
 
   ## What is the purpose of the change
   
   Upgrade flink-table Calcite version to 1.22.0, including module: 
`flink-sql-parser`, `flink-table-planner`, `flink-table-planner-blink`.
   
   
   ## Brief change log
   The change was split into 12 commits, each commit has detail commit messages 
there ~
   
     - *Bump sql parser Calcite dependency to 1.22.0*
     - *Implements new RelMetadataQuery extension*
     - *Remove usage of TableScanRule and use new TableScanFactory extension*
     - *Tweak implementations due to API change*
     - *Remove redundant code copy because the bugs are already fixed in 
Calcite*
     - *table-planner-blink: Plan verify changes from DIGEST to EXPLAIN*
     - *table-planner-blink: Plan verify changes from DIGEST to EXPLAIN: change 
plan for explain node*
     - *table-planner-blink: Plan verify changes from DIGEST to EXPLAIN: change 
plan for values node*
     - *Update files due to builtin TUMBLE operator name changes to $Tumble*
     - *Update files due to CALCITE-3763*
     - *Update files due to CALCITE-1824*
     - *Update all kinds of left plan changes*
   
   
   
   ## Verifying this change
   
   Testing through existing test set.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): yes
     - 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/Mesos, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to