godfreyhe opened a new pull request #9213: [FLINK-13266] [table] Relocate blink 
planner classes to avoid class clashes (for release-1.9)
URL: https://github.com/apache/flink/pull/9213
 
 
   
   ## What is the purpose of the change
   
   *Relocate blink planner classes to avoid class clashes (for release-1.9), 
see the relocation part in 
https://docs.google.com/document/d/15Z1Khy23DwDBp956yBzkMYkGdoQAU_QgBoJmFWSffow*
   
   
   ## Brief change log
   
     - *move OptimizerConfigOptions & ExecutionConfigOptions to table-api-java 
module*
     - *move ExpressionParserException & UnresolvedException to table-common 
module*
     - *remove definedTimeAttributes file in blink planner*
     - *move DataView related classes to table-common module, and remove 
duplicate classes*
     - *remove Order class from table-runtime-blink*
     - *port descriptors to table-common*
     - *Improve comment for FilterableTableTableSource*
     - *Relocate blink runtime classes to avoid class clashes*
     - *Relocate blink planner classes to avoid class clashes*
   
   ## Verifying this change
   
   no new tests and the existing tests should pass
   
   ## 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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to