Github user alpinegizmo commented on a diff in the pull request:
https://github.com/apache/flink/pull/3858#discussion_r115701327
--- Diff: docs/dev/stream/checkpointing.md ---
@@ -124,8 +124,8 @@ env.getCheckpointConfig.setMaxConcurrentCheckpoints(1)
## Selecting a State Backend
-The checkpointing mechanism stores the progress in the data sources and
data sinks, the state of windows, as well as the [user-defined
state](state.html) consistently to
-provide *exactly once* processing semantics. Where the checkpoints are
stored (e.g., JobManager memory, file system, database) depends on the
configured
+The checkpointing mechanism stores consistent snapshots of the progress in
the data sources and data sinks, the state of windows and timers, as well as
any [user-defined state](state.html), thereby
--- End diff --
After spending more time with this, my conclusion is that getting into
"exactly once processing semantics" is off-topic in a short section whose
purpose is to introduce the idea of state backends. What I've done instead is
to beef up the linking between the various related pages.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
