alpinegizmo commented on a change in pull request #14236:
URL: https://github.com/apache/flink/pull/14236#discussion_r531075132
##########
File path: docs/dev/datastream_execution_mode.md
##########
@@ -38,12 +38,18 @@ for which you have a known fixed input and which do not run
continuously.
Apache Flink's unified approach to stream and batch processing means that a
DataStream application executed over bounded input will produce the same
-results regardless of the configured execution mode. By enabling `BATCH`
-execution, we allow Flink to apply additional optimizations that we can only do
-when we know that our input is bounded. For example, different join/aggregation
-strategies can be used, in addition to a different shuffle implementation that
-allows more efficient task scheduling and failure recovery behavior. We will go
-into some of the details of the execution behavior below.
+*final* results regardless of the configured execution mode. It is important to
+note what *final* means here: a job executing in `STREAMING` mode might produce
+incremental updates (think upserts in a data base) while a `BATCH` job would
Review comment:
```suggestion
incremental updates (think upserts in a database) while a `BATCH` job would
```
----------------------------------------------------------------
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:
[email protected]
