WeiZhong94 opened a new pull request #8267: [FLINK-12311][table][python] Add 
base python framework and Add Scan, Projection, and Filter operator support
URL: https://github.com/apache/flink/pull/8267
 
 
   
   ## What is the purpose of the change
   
   *This pull request adds the basic functionalities for Python Table API. Only 
Scan, Projection, and Filter operator will be supported in this PR.*
   
   
   ## Brief change log
   
     - *Add a `flink-python` module with a submodule `flink-python-table` under 
flink-parent.*
     - *Add `pyflink2.sh` on `flink-dist` module for launching Py4J Java 
Gateway Server.*
     - *Add a minimal implementation of the Flink Python Table API that only 
support Scan, Projection, and Filter operator.*
     - *Add documents for Scan, Projection, and Filter operator of the Python 
Table API.*
     - *Add a simple end to end test for Python Table API.*
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - *Manually verified the change by building the whole project using `mvn 
clean package`, entering the directory 
`$FLINK_HOME/flink-python/flink-python-table/src/main/python`, and running 
`PYTHONPATH=./ python ./pyflink/table/tests/test_end_to_end.py`, verifying the 
program runs correctly and no exception raised.*
   
   ## 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? (yes)
     - 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 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