You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/12/07 14:18:25 UTC

[GitHub] [flink] godfreyhe opened a new pull request #10480: [FLINK-15095] [table-planner-blink] bridge table schema's primary key to metadata handler in blink planner

godfreyhe opened a new pull request #10480: [FLINK-15095] [table-planner-blink] bridge table schema's primary key to metadata handler in blink planner
URL: https://github.com/apache/flink/pull/10480
 
 
   
   ## What is the purpose of the change
   
   *bridge table schema's primary key to metadata handler in blink planner. current approach is a temporary solution, [FLINK-15123](https://issues.apache.org/jira/browse/FLINK-15123) will resolve this*
   
   
   ## Brief change log
   
     - *bridge table schema's primary key to FlinkStatistic in DatabaseCalciteSchema*
   
   
   ## Verifying this change
   
   
   
   This change added tests and can be verified as follows:
   
     - *Added CatalogConstraintTest to verify whether the primary key is used in metadata handler*
   
   ## 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:
users@infra.apache.org


With regards,
Apache Git Services