This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/hop-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 95dbc93dc5 Website updated to 45a48e9
95dbc93dc5 is described below
commit 95dbc93dc5360ba7b32dd24c1c091eaa5914e320
Author: jenkins <[email protected]>
AuthorDate: Tue Sep 22 11:14:40 2026 +0000
Website updated to 45a48e9
---
manual/next/how-to-guides/cdc-log-sniffing.html | 3 +++
manual/next/pipeline/pipeline-unit-testing.html | 2 +-
manual/next/pipeline/transforms/kafkaconsumer.html | 12 +++++++++++-
3 files changed, 15 insertions(+), 2 deletions(-)
diff --git a/manual/next/how-to-guides/cdc-log-sniffing.html
b/manual/next/how-to-guides/cdc-log-sniffing.html
index a48097b7af..d9f11529f5 100644
--- a/manual/next/how-to-guides/cdc-log-sniffing.html
+++ b/manual/next/how-to-guides/cdc-log-sniffing.html
@@ -2957,6 +2957,9 @@ Switch / Case or Filter Rows (route on
operation)
<li>
<p><strong>Scheduled drain</strong>: enable <strong>Stop when idle</strong>
(and an idle timeout) so a workflow can start the pipeline, empty the topic,
and finish. That is the “queue + schedule” pattern.</p>
</li>
+<li>
+<p><strong>Timed window</strong>: set <strong>Max consume duration
(ms)</strong> when the topic never goes idle (a low continuous trickle) but you
still want a scheduled run to process for a fixed time and then finish.</p>
+</li>
</ul>
</div>
<div class="paragraph">
diff --git a/manual/next/pipeline/pipeline-unit-testing.html
b/manual/next/pipeline/pipeline-unit-testing.html
index 966c373b8d..e233cbf3e9 100644
--- a/manual/next/pipeline/pipeline-unit-testing.html
+++ b/manual/next/pipeline/pipeline-unit-testing.html
@@ -3053,7 +3053,7 @@ By default, you should see the active pipeline filename
here.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Replace a
database connection with another</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">specify a
list of database connections for this pipeline that you’d like to swap
out for a test-specific connection.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">specify a
list of database connections for this pipeline that you’d like to swap
out for a test-specific connection. The swap rewrites those relational
connection references on the in-memory test copy, including lookups, and does
not change the project connection.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p
class="tableblock">Variables</p></td>
diff --git a/manual/next/pipeline/transforms/kafkaconsumer.html
b/manual/next/pipeline/transforms/kafkaconsumer.html
index 879330de4e..dd86d627ca 100644
--- a/manual/next/pipeline/transforms/kafkaconsumer.html
+++ b/manual/next/pipeline/transforms/kafkaconsumer.html
@@ -2859,10 +2859,11 @@ Topics are divided into a set of logs known as
partitions.</p>
<div class="paragraph">
<p>By default the Kafka consumer transform continuously ingests streaming data.
To stop after the topic has been drained, enable <strong>Stop when
idle</strong> on the Batch tab (with an optional max idle time).
+To consume for a fixed wall-clock window even when messages keep arriving, set
<strong>Max consume duration (ms)</strong> (for example 15 minutes once per
hour).
You can also use the Abort transform in your parent or sub-pipeline to stop
consuming records for other conditions.</p>
</div>
<div class="paragraph">
-<p>For example, you can run the parent pipeline on a timed schedule, drain a
topic once per hour with stop-when-idle, or abort the sub-pipeline if sensor
data exceeds a preset range.</p>
+<p>For example, you can run the parent pipeline on a timed schedule, drain a
topic once per hour with stop-when-idle, consume for a fixed duration on a
topic that never goes idle, or abort the sub-pipeline if sensor data exceeds a
preset range.</p>
</div>
</div>
</div>
@@ -2982,6 +2983,15 @@ Defaults to 500.
Supports variables.</p></td>
</tr>
<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Max
consume duration (ms)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Maximum
time in milliseconds to consume since the transform started.
+This is not the batch <strong>Duration (ms)</strong> field: batch duration
only controls how long each poll waits for a batch.
+When this limit is reached the transform finishes gracefully after the current
batch is processed and committed.
+0 or empty means no limit (the default).
+<strong>Stop when idle</strong> can still finish earlier if the topic goes
quiet first.
+Supports variables.</p></td>
+</tr>
+<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Offset
management</p></td>
<td class="tableblock halign-left valign-top"><div class="content"><div
class="paragraph">
<p>Choose when to commit</p>
