bowenli86 opened a new pull request #8541: [FLINK-9172][sql-client] Support 
catalogs in SQL-Client yaml config file
URL: https://github.com/apache/flink/pull/8541
 
 
   ## What is the purpose of the change
   
   This PR adds support for **basic** catalog entries in SQL-Client yaml config 
file, adds `CatalogFactory` and `CatalogDescriptor`, and hooks them up with SQL 
Client thru table factory discovery service.
   
   Please refer to the design in 
[doc](https://docs.google.com/document/d/1ALxfiGZBaZ8KUNJtoT443hReoPoJEdt9Db2wiJ2LuWA/edit).
   
   Note that more fields of catalog entries and factories for existing catalogs 
will be added in the next few PRs. 
   
   ## Brief change log
   
   - Created `CatalogFactory`, `CatalogDescriptor`, 
`CatalogDescriptorValidator` in flink table modules
   - Created `CatalogEntry` and made SQL CLI handle catalog entries in yaml file
   - Added unit tests
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
   - see new unit tests in this PR
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes)
     - 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? (yes)
     - If yes, how is the feature documented? docs will be added later when the 
feature completes
   

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