dawidwys opened a new pull request #8764:  
[FLINK-12798][table-planner][table-api-java] Port TableEnvironment to 
table-api-java module
URL: https://github.com/apache/flink/pull/8764
 
 
   ## What is the purpose of the change
   
   This PR moves `TableEnvironment`s & `TableImpl` to the proper api modules. 
It adds `Executor` module that abstracts away `StreamExecutionEnvironment` from 
the unfied `TableEnvironment`. 
   
   The `Executor`, `Planner` and `OperationTreeBuilder`(temporarily) are looked 
up by reflection.
   
   In this PR the `StreamQueryConfig` is passed via `PlannerConfig`. This might 
change in the future if we rework the `TableConfig`.
   
   This PR does not enable `Planner` switching yet. It works only with the 
legacy Planner. The `Planner` instantiation via configuration will be 
introduced later.
   
   It adds an `execute` method to the `TableEnvironment` to enable lazy 
execution and thus optimizing more queries at the same time.
   
   It is based on #8739 
   
   ## Verifying this change
   
   
   This change is already covered by existing tests.
   
   ## 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