[GitHub] [flink] dawidwys opened a new pull request #8404: [FLINK-11476][table] Create CatalogManager to manage multiple catalogs

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

dawidwys opened a new pull request #8404: [FLINK-11476][table] Create CatalogManager to manage multiple catalogs
URL: https://github.com/apache/flink/pull/8404
 
 
   ## What is the purpose of the change
   
   This PR adds a `CatalogManager` that stores tables and resolves paths accordingly.
   
   ## Brief change log
   
     - added `CatalogManager` implementation with logic for resolving tables using also the default path
     - 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`
     - **Added `Catalog` related APIs to `TableEnvironment`**
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - All existent tests should pass
     - `org.apache.flink.table.catalog.CatalogManagerTest`
     - `org.apache.flink.table.catalog.CatalogManagerPathResolutionTest`
   
   ## 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