dawidwys opened a new pull request #8549: 
[FLINK-12604][table-api][table-planner] Register TableSource/Sink as 
CatalogTables
URL: https://github.com/apache/flink/pull/8549
 
 
   ## What is the purpose of the change
   
   This is next step in decoupling `TableEnvironment` from Calcite. It 
introduces registration of `TableSource/Sink` as `CatalogTable`s.
   
   ## Brief change log
   
   This is based on #8521.
   
     - added `org.apache.flink.table.catalog.ConnectorCatalogTable` that wraps 
`TableSource/Sink` and used it for registration in `TableEnvironment`
     - added `org.apache.flink.table.operations.TableSourceTableOperation` for 
reading from an inline `TableSource`. This is used only when creating a `Table` 
from `TableEnvironment#fromTableSource` 
     - removed unnecessary code duplication from classes such as 
`TableSourceSinkTable`, `TableSourceTable`, `TableSinkTable` etc.
   
   
   ## Verifying this change
   
   * This change is already covered by existing tests.
   * Added test to verify `TableEnviroment#fromTableSource` behavior: 
`org.apache.flink.table.runtime.stream.table.TableSourceITCase#testInlineCsvTableSource`
   
   
   ## 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:
[email protected]


With regards,
Apache Git Services

Reply via email to