TsReaper opened a new pull request #12037:
URL: https://github.com/apache/flink/pull/12037


   ## What is the purpose of the change
   
   This PR is part of the 
[FLINK-14807](https://issues.apache.org/jira/browse/FLINK-14807) which is going 
to introduce a collecting method for tables. See 
[here](https://docs.google.com/document/d/13Ata18-e89_hAdfukzEJYreOg2FBZO_Y0RohLDAme6Y/edit)
 for the whole design document.
   
   To allow the clients to receive results from the coordinator, which acts as 
a proxy between the clients and the sinks, a communication protocol should be 
introduced between the clients and the coordinators. This PR introduce this new 
communication protocol through the REST API.
   
   Note that as coordinators are internally used only, we're not going to 
expose this REST API to the user, thus no user document is provided.
   
   ## Brief change log
   
    - Introduce a REST API to allow the communication between clients and 
coordinators.
   
   ## Verifying this change
   
   This PR is only an internal API change without real usage. This change can 
be tested after the whole collecting mechanism is introduced.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - 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, Kubernetes/Yarn/Mesos, ZooKeeper: yes (JobManager)
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? yes
     - If yes, how is the feature documented? 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


Reply via email to