walterddr opened a new pull request #7607: [FLINK-10076][table] Upgrade Calcite 
dependency to 1.18
URL: https://github.com/apache/flink/pull/7607
 
 
   
   
   ## What is the purpose of the change
   
   Upgrade Calcite dependency to 1.18 for flink-table package. including 
various bug fixes and improvements ( details can be found in JIRA discussion )
   
   
   ## Brief change log
   - Fix TimeIndicator type optimization 
     - Due to: [CALCITE-1413], [CALCITE-2695] 
     - Fix: include `digest` for `TimeIndicatorRelDataType`
   - Under-simplify rexcall chain
     - Due to: [CALCITE-2726] RexSimplify does not simplify enough for some of 
the nested operations, doesn't do nested visitCall
     - Fix: updated tests, future fixes needed on calcite
   - Remove duplicated expressions & Casting optimization
     - Due to: [CALCITE-1413], [CALCITE-2631], [CALCITE-2639]
     - Fix: update tests
   - Nested selected time indicator type not working properly 
   --> Due to: [CALCITE-2470], project method combines expressions if the 
underlying node is a project; Fix: pulled in `RelBuilder` from calcite and 
changes flag to not optimize project merge.
   
   ## Verifying this change
   
   This change is already covered by existing tests.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): yes
       - Updated Calcite dependency and list of exclusions
     - 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? N/A
   

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