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 2019/06/24 20:11:43 UTC

[GitHub] [flink] sjwiesman opened a new pull request #8861: [FLINK-12963][state-processor-api] Add savepoint writer for bootstrapping new savepoints

sjwiesman opened a new pull request #8861: [FLINK-12963][state-processor-api] Add savepoint writer for bootstrapping new savepoints
URL: https://github.com/apache/flink/pull/8861
 
 
   ## What is the purpose of the change
   
   Introduce a savepoint writer for bootstrapping state. 
   
   
   ## Brief change log
   This is based on #8618 and only the last 4 commits are relevant. 
   
   b341e91  Introduces the new runtime components for running a bounded stream task and snapshotting its contents after processing all elements. **Note** this is the most important commit. 
   
   830ac6a Add user-facing interfaces and corresponding stream operators. 
   
   f12439f Adds the user api 
   
   
   b0f176e  Update the travis profile so that the state processor api is run during the libraries stage
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   UT and IT test
   
   ## 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: no
     - 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 (I am working on the docs and will push when complete)
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services