[GitHub] [flink] godfreyhe opened a new pull request #8707: [FLINK-12815] [table-planner-blink] Supports CatalogManager in blink planner

[GitBox <gi...@apache.org>]

godfreyhe opened a new pull request #8707: [FLINK-12815] [table-planner-blink] Supports CatalogManager in blink planner
URL: https://github.com/apache/flink/pull/8707
 
 
   
   
   ## What is the purpose of the change
   
   *Supports CatalogManager in blink planner (which is what FLINK-11476 has done)*
   
   
   ## Brief change log
   
     - *all table registrations and lookups in TableEnvironment go through CatalogManager*
     - *added Calcite's Schema structure corresponding to the CatalogManager. This enables Calcite to lookup for Tables through CatalogManager*
     - *introduce CrudExternalCatalog and InMemoryExternalCatalog and catalog exceptions*
     - *add FileSystem and OldCsv descriptors for test*
   
   
   ## Verifying this change
   
   
   This change added tests and can be verified as follows:
   
     - *All existent tests should pass, except catalog name and database name are added to table scan digest*
     - *Added test that validates CatalogManager logic in blink planner*
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (not applicable / docs / JavaDocs / **not documented**)
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services