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


   ## Pre-review note
   
   This PR is waiting for #12037 to merge. The 1st commit is exactly the same 
with the blocking PR. Please start reviewing from the 2nd commit. This PR will 
be rebased once the blocking PR is merged.
   
   ## 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.
   
   This PR introduces a specialized collecting sink function and its 
coordinator.
   * The coordinator acts as a proxy between the client and the sink function 
to work around under the environment where clients can't directly talk to task 
managers.
   * The sink function uses a simple to handle failures in order to achieve 
exactly-once semantics. See the design document for details.
   
   ## Brief change log
   
   - Add specialized collecting sink function and its coordinator
   
   ## Verifying this change
   
   This change can be verified by running the newly added unit tests.
   
   ## 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: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? no
   


----------------------------------------------------------------
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