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/01/28 14:17:59 UTC

[GitHub] twalthr opened a new pull request #7587: [FLINK-11064] [table] Setup a new flink-table module structure

twalthr opened a new pull request #7587: [FLINK-11064] [table] Setup a new flink-table module structure
URL: https://github.com/apache/flink/pull/7587
 
 
   ## What is the purpose of the change
   
   This commit splits the flink-table module into multiple submodules in accordance with FLIP-32 (step 1).
   
   The module structure assumes that the type system has been reworked such that only one table environment exists for both Java and Scala users. If this change won't happen, we will introduce a `flink-table-api-base` interally but this won't affect 
   
   The new module structure looks as follows:
   
   flink-table-common
          ^
          |
   flink-table-api-java <------- flink-table-api-scala
          ^                                 ^
          |                                 |
   flink-table-api-java-bridge    flink-table-api-scala-bridge
          ^
          |
   flink-table-planner
   
   The module flink-table-planner contains the content of the old flink-table module. From there we can distribute ported classes to their final module without breaking backwards compatibility or force users to update their dependencies again.
   
   If a user wants to implement a pure table program in Scala, flink-table-api-scala and flink-table-planner need to be added to the project.
   
   Until we support pure table programs, flink-table-api-scala/java-bridge and flink-table-planner need to be added to the project.
   
   If a user only wants to implement a UDF or format, flink-table-common needs to be added.
   
   All Flink modules have been updated to the new dependency design. End-to-end tests succeed and docs have been updated.
   
   ## Brief change log
   
   - Maven module structure updated
   
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as SQL Client and Stream SQL end-to-end tests.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): yes
     - 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? docs
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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