Skip to content

Commit daacf07

Browse files
authored
Fix watermark alignment explanation in documentation
according to the following description and the flag should be false,then make sense.
1 parent 03aa8c8 commit daacf07

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/content/docs/dev/datastream/event-time/generating_watermarks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -271,7 +271,7 @@ If you are upgrading from a Flink version between 1.15.x and 1.16.x inclusive, y
271271
by checking if it throws an `UnsupportedOperationException` at runtime or by reading the javadocs. In this case, it would be desirable to
272272
to disable split level watermark alignment to avoid fatal exceptions.
273273

274-
When setting the flag to true, watermark alignment will be only working properly when the number of splits/shards/partitions is equal to the
274+
When setting the flag to false, watermark alignment will be only working properly when the number of splits/shards/partitions is equal to the
275275
parallelism of the source operator. This results in every subtask being assigned a single unit of work. On the other hand, if there are two Kafka partitions, which produce watermarks at different paces and
276276
get assigned to the same task, then watermarks might not behave as expected. Fortunately, even in the worst case, the basic alignment should not perform worse than having no alignment at all.
277277

0 commit comments

Comments
 (0)