You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by se...@apache.org on 2015/07/06 15:32:55 UTC

flink git commit: [docs] Fix formatting error in description of stream checkpointing

Repository: flink
Updated Branches:
  refs/heads/master 728a5261e -> 0cb9eb59e


[docs] Fix formatting error in description of stream checkpointing


Project: http://git-wip-us.apache.org/repos/asf/flink/repo
Commit: http://git-wip-us.apache.org/repos/asf/flink/commit/0cb9eb59
Tree: http://git-wip-us.apache.org/repos/asf/flink/tree/0cb9eb59
Diff: http://git-wip-us.apache.org/repos/asf/flink/diff/0cb9eb59

Branch: refs/heads/master
Commit: 0cb9eb59ea4a968970c6280e4c72e220bacdbb42
Parents: 728a526
Author: Stephan Ewen <se...@apache.org>
Authored: Mon Jul 6 15:31:48 2015 +0200
Committer: Stephan Ewen <se...@apache.org>
Committed: Mon Jul 6 15:31:48 2015 +0200

----------------------------------------------------------------------
 docs/internals/stream_checkpointing.md | 1 +
 1 file changed, 1 insertion(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/flink/blob/0cb9eb59/docs/internals/stream_checkpointing.md
----------------------------------------------------------------------
diff --git a/docs/internals/stream_checkpointing.md b/docs/internals/stream_checkpointing.md
index d36f569..9fee117 100644
--- a/docs/internals/stream_checkpointing.md
+++ b/docs/internals/stream_checkpointing.md
@@ -105,6 +105,7 @@ When operators contain any form of *state*, this state must be part of the snaps
 Operators snapshot their state at the point in time when they received all snapshot barriers from their input streams, before emitting the barriers to their output streams. At that point, all updates to the state from records before the barriers will have been made, and no updates that depend on records from after the barriers have been applied. Because the state of a snapshot may be potentially large, it is stored in a configurable *state backend*. By default, this is the JobManager's memory, but for serious setups, a distributed reliable storage should be configured (such as HDFS). After the state has been stored, the operator acknowledges the checkpoint, emity the snapshot barrier into the output streams, and proceeds.
 
 The resulting snapshot now contains:
+
   - For each parallel stream data source, the offset/position in the stream when the snapshot was started
   - For each operator, a pointer to the state that was stored as part of the snapshot