danny0405 opened a new pull request #10224: [FLINK-14716][table-planner-blink] 
Cooperate computed column with push down rules
URL: https://github.com/apache/flink/pull/10224
 
 
   ## What is the purpose of the change
   
   This patch make some refactor to the `FlinkTable` and its sub-class. Also 
add some tests for computed column and push down rules.
   
   
   ## Brief change log
   
   * Remove FlinkTable, add a new RelOptTable abstract implementation named 
FlinkPreparingTableBase and make all the Flink specific tables extend it.
   * Remove FlinkRelOptTable and use the sub-class of FlinkPreparingTableBase
   * Remove TableSinkTable and TableSourceSinkTable because they are all useless
   * Merge InlineTable into DataStreamTable because which is the only 
implementation
   
   * Postpone the Flink tables translation from DatabaseCalciteSchema to 
FlinkCalciteCatalogReader which happens during sql-to-rel conversion
   * In DatabaseCalciteSchema, introduce a new class named CatalogSchemaTable 
to bridge the schema table and catalog table
   
   * Fix the files that reference the changed tables.
   * Promote the TableSourceUtil row type inference.
   
   * Refactor MetadataTestUtil to use mock FlinkPreparingBaseTable
   * Fix the flink specific table reference code
   
   * Add test case for computed column with push down rules.
   
   
   ## Verifying this change
   The tests are added to the exiting files.
   
   ## 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)`: no
     - 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? no
     - If yes, how is the feature documented? 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