This is an automated email from the ASF dual-hosted git repository.

pnowojski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git

commit 68aca153e0a2dc24b0751810f66db4a46da5b275
Author: Piotr Nowojski <[email protected]>
AuthorDate: Mon Apr 7 19:01:35 2025 +0200

    [FLINK-37399][docs] Regenerate docs
---
 docs/layouts/shortcodes/generated/pipeline_configuration.html | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/layouts/shortcodes/generated/pipeline_configuration.html 
b/docs/layouts/shortcodes/generated/pipeline_configuration.html
index f8b511206c7..e4050aee746 100644
--- a/docs/layouts/shortcodes/generated/pipeline_configuration.html
+++ b/docs/layouts/shortcodes/generated/pipeline_configuration.html
@@ -134,5 +134,11 @@
             <td>Boolean</td>
             <td>If watermark alignment is used, sources with multiple splits 
will attempt to pause/resume split readers to avoid watermark drift of source 
splits. However, if split readers don't support pause/resume, an 
UnsupportedOperationException will be thrown when there is an attempt to 
pause/resume. To allow use of split readers that don't support pause/resume 
and, hence, to allow unaligned splits while still using watermark alignment, 
set this parameter to true. The default value  [...]
         </tr>
+        <tr>
+            <td><h5>pipeline.watermark-alignment.buffer-size</h5></td>
+            <td style="word-wrap: break-word;">3</td>
+            <td>Integer</td>
+            <td>Controls size of the ring buffer used to smooth out watermark 
alignment due to the inherent latency of the alignment process. Allowed 
watermarks are announced at the updateInterval and this means they are often 
out of date after the round trip, which means that watermark alignment might be 
pausing splits too much using this outdated information. To address this 
problem, when pausing consumption of records, max allowed watermark is not 
checked against the latest value of t [...]
+        </tr>
     </tbody>
 </table>

Reply via email to