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 2018/11/03 13:35:55 UTC

[GitHub] buptljy opened a new pull request #7013: [FLINK-5601][Checkpointing] Watermark checkpointing

buptljy opened a new pull request #7013: [FLINK-5601][Checkpointing] Watermark checkpointing
URL: https://github.com/apache/flink/pull/7013
 
 
   ## What is the purpose of the change
   
   This pull request uses ListState in TimestampsAndPeriodicWatermarksOperator.java and TimestampsAndPunctuatedWatermarksOperator.java to checkpoint watermark. During recovering process, it uses union state to find the lowest watermark and emit it immediately.
   
   ## Brief change log
   * Add ListState to store watermark in TimestampsAndPeriodicWatermarksOperator.java and TimestampsAndPunctuatedWatermarksOperator.java.
   
   ## Verifying this change
   
   * Unit testing in WatermarkCheckpointingITCase.java. 
       * TimestampsAndPeriodicWatermarksOperator testing:  Send five "Five", then checkpoint, then make the job fail, then recover the job, and send five "Three", the sum should be 25.
       * TimestampsAndPunctuatedWatermarksOperator testing: Similar testing logic machenism as above.
   
   ## 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, Yarn/Mesos, ZooKeeper: yes
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? 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 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