JingsongLi opened a new pull request #11047: [FLINK-15912][table] Add Context 
to TableSourceFactory and TableSinkFactory
URL: https://github.com/apache/flink/pull/11047
 
 
   
   ## What is the purpose of the change
   
   Discussion in: 
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Improve-TableFactory-td36647.html
   
   Vote in: 
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/VOTE-Improve-TableFactory-to-add-Context-td37211.html
   
   Motivation:
   Now the main needs and problems are:
   
   Connector can't get TableConfig[1], and some behaviors really need to be
   controlled by the user's table configuration. In the era of catalog, we
   can't put these config in connector properties, which is too inconvenient.
   A context class also allows for future modifications without touching the 
TableFactory interface again.
   
   ## Brief change log
   
   1. Interface modification for table factories
   2. Apply new interface in blink planner.
   
   ## Verifying this change
   
   `CatalogTableITCase.testTableSourceSinkFactory`
   
   ## 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)
     - 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:
[email protected]


With regards,
Apache Git Services

Reply via email to