dawidwys opened a new pull request #8852:  
[FLINK-12798][table-api][table-planner] Add a proper discover mechanism that 
will  enable switching between Flink & Blink Planner/Executor
URL: https://github.com/apache/flink/pull/8852
 
 
   ## What is the purpose of the change
   
   This PR improves the lookup mechanism for `Planner` & `Executor` to enable 
switching between Flink & Blink planner components/
   
   
   ## Brief change log
   
     - Improved type handling in `TableFactoryService`
     - Enabled returning multiple matching `TableFactory`s from 
`TableFactoryService`
     - Added `ExecutorFactory` & `PlannerFactory` that can be discovered based 
on string properties
     - Added `PlannerDescriptor` to enable switching between different planner 
components in the API.
   
   
   ## Verifying this change
   
   This change is already covered by existing tests.
   Added tests for disambiguating factories based on `optionalContext`: 
`org.apache.flink.table.factories.ComponentFactoryServiceTest`
   
   
   ## 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**): should be added as a follow-up as part of major rework 
of docs for the updated Table API
   

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