jamesstarr opened a new pull request #2475:
URL: https://github.com/apache/calcite/pull/2475


   Removing planner.registerMetadataProviders(a noop call) from
   RelOptTest.checkPlanning.  Reworking
   RelMetadataTest.testMetadataHandlerCacheLimit to use an anonymous inner
   class instead of CachingRelMetadataProvider since the only property
   requiere to reproduce the bug is a wrapper of a RelMetadataProvider.
   
   Deprecating:
   * RelOptPlanner.registerMetadataProviders - Used to support custom nodes
     in reflection based rel metadata.  The generated code based rel
     metadata has tight couple so this is not needed.
   * RelOptPlanner.getRelMetadataTimestamp - Used for cache invalidation in
     reflection based rel metadata.  The generated code based rel
     metadata has tight couple so this is not needed.
   *.RelOptCluster.metadataFactory - Exposing an api for reflection based
     rel metadata.
   * RelNode.metadata - An api for accessing reflection based rel metadata.
   * CachingRelMetadataProvider - Implements caching for reflection based
     rel metadata.  Generated code base rel metadata use a Table in
     RelMetadataQuery and tight coupling for caching.
   *.RelMetadataProvider.apply - The primary entry point reflection based
     rel metadata.
   * MetadataFactory - An api for reflection based rel metadata.
   * MockRelOptPlanner.setRelMetadataTimestamp - Used in testing reflection
     based rel metadata.
   * ReflectiveRelMetadataProvider.{map, metadataClass0 - Used in the
     implementation reflection based rel metadata.
   * VolcanoRelMetadataProvider - Supports custom volcanno rels in
     reflection based rel metadata.
   *.HepRelMetadataProvider - Supports custom hep rels in reflection based
     rel metadata.


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