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 67677a27cd Website updated to ce72275
67677a27cd is described below
commit 67677a27cd30da49707d79115c06b4f2bbf31421
Author: jenkins <[email protected]>
AuthorDate: Sat Nov 14 16:05:54 2026 +0000
Website updated to ce72275
---
manual/next/metadata-types/pipeline-log.html | 11 +++++++++++
manual/next/metadata-types/pipeline-probe.html | 11 +++++++++++
manual/next/metadata-types/workflow-log.html | 11 +++++++++++
.../spark/getting-started-with-native-spark.html | 2 +-
manual/next/pipeline/transforms/abort.html | 8 ++++++++
manual/next/pipeline/transforms/accessoutput.html | 9 +++++++++
manual/next/pipeline/transforms/addchecksum.html | 18 ++++++++++++++++++
manual/next/pipeline/transforms/addconstant.html | 8 ++++++++
manual/next/pipeline/transforms/addsequence.html | 18 ++++++++++++++++++
manual/next/pipeline/transforms/addxml.html | 8 ++++++++
manual/next/pipeline/transforms/analyticquery.html | 18 ++++++++++++++++++
manual/next/pipeline/transforms/append.html | 8 ++++++++
manual/next/pipeline/transforms/aws-sns-notify.html | 9 +++++++++
manual/next/pipeline/transforms/aws-sqs-reader.html | 9 +++++++++
.../pipeline/transforms/azure-event-hubs-listener.html | 9 +++++++++
.../pipeline/transforms/azure-event-hubs-writer.html | 9 +++++++++
manual/next/pipeline/transforms/blockingtransform.html | 8 ++++++++
.../transforms/blockuntiltransformsfinish.html | 9 +++++++++
manual/next/pipeline/transforms/calculator.html | 18 ++++++++++++++++++
manual/next/pipeline/transforms/calldbproc.html | 9 +++++++++
.../next/pipeline/transforms/changefileencoding.html | 8 ++++++++
manual/next/pipeline/transforms/checkfilelocked.html | 8 ++++++++
manual/next/pipeline/transforms/jsoninput.html | 18 ++++++++++++++++++
.../next/pipeline/transforms/jsonnormalizeinput.html | 18 ++++++++++++++++++
manual/next/pipeline/transforms/pipeline-executor.html | 3 ++-
manual/next/pipeline/transforms/serialize-to-file.html | 7 +++++++
manual/next/pipeline/transforms/zipfile.html | 6 ++++++
27 files changed, 276 insertions(+), 2 deletions(-)
diff --git a/manual/next/metadata-types/pipeline-log.html
b/manual/next/metadata-types/pipeline-log.html
index 3abd6ac8d0..ee9e5c4e77 100644
--- a/manual/next/metadata-types/pipeline-log.html
+++ b/manual/next/metadata-types/pipeline-log.html
@@ -3017,6 +3017,17 @@ In this logging pipeline, you can process the logging
information and e.g. write
</div>
</div>
<div class="sect1">
+<h2 id="_when_changes_take_effect"><a class="link"
href="#_when_changes_take_effect">When changes take effect</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>A run reads the pipeline logs once, when it first needs them, and every
pipeline and workflow it starts uses what it read: the child pipelines of a
Pipeline executor, the pipelines of a workflow, a mapping and so on. A run is a
top-level pipeline or workflow, the one that Hop Run, Hop GUI, Hop Server or
the API starts.</p>
+</div>
+<div class="paragraph">
+<p>A pipeline log that you add or change while a run is going on takes effect
with the next run. This matters for runs that go on for a long time, such as a
workflow that loops for hours or a streaming pipeline.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
<div class="sectionbody">
<div class="paragraph">
diff --git a/manual/next/metadata-types/pipeline-probe.html
b/manual/next/metadata-types/pipeline-probe.html
index 5b0febbf26..32d85289fb 100644
--- a/manual/next/metadata-types/pipeline-probe.html
+++ b/manual/next/metadata-types/pipeline-probe.html
@@ -3019,6 +3019,17 @@
</div>
</div>
<div class="sect1">
+<h2 id="_when_changes_take_effect"><a class="link"
href="#_when_changes_take_effect">When changes take effect</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>A run reads the pipeline probes once, when it first needs them, and every
pipeline and workflow it starts uses what it read: the child pipelines of a
Pipeline executor, the pipelines of a workflow, a mapping and so on. A run is a
top-level pipeline or workflow, the one that Hop Run, Hop GUI, Hop Server or
the API starts.</p>
+</div>
+<div class="paragraph">
+<p>A pipeline probe that you add or change while a run is going on takes
effect with the next run. This matters for runs that go on for a long time,
such as a workflow that loops for hours or a streaming pipeline.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
<h2 id="_related_plugins"><a class="link" href="#_related_plugins">Related
Plugins</a></h2>
<div class="sectionbody">
<div class="ulist">
diff --git a/manual/next/metadata-types/workflow-log.html
b/manual/next/metadata-types/workflow-log.html
index 8b024b1d5c..c89e5a6017 100644
--- a/manual/next/metadata-types/workflow-log.html
+++ b/manual/next/metadata-types/workflow-log.html
@@ -3017,6 +3017,17 @@ In this logging pipeline, you can process the logging
information and e.g. write
</div>
</div>
<div class="sect1">
+<h2 id="_when_changes_take_effect"><a class="link"
href="#_when_changes_take_effect">When changes take effect</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>A run reads the workflow logs once, when it first needs them, and every
pipeline and workflow it starts uses what it read: the child pipelines of a
Pipeline executor, the pipelines of a workflow, a mapping and so on. A run is a
top-level pipeline or workflow, the one that Hop Run, Hop GUI, Hop Server or
the API starts.</p>
+</div>
+<div class="paragraph">
+<p>A workflow log that you add or change while a run is going on takes effect
with the next run. This matters for runs that go on for a long time, such as a
workflow that loops for hours or a streaming pipeline.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
<div class="sectionbody">
<div class="paragraph">
diff --git a/manual/next/pipeline/spark/getting-started-with-native-spark.html
b/manual/next/pipeline/spark/getting-started-with-native-spark.html
index e027ff6d90..c679b15159 100644
--- a/manual/next/pipeline/spark/getting-started-with-native-spark.html
+++ b/manual/next/pipeline/spark/getting-started-with-native-spark.html
@@ -4198,7 +4198,7 @@ Examples: sorted <strong>Group By</strong> (use
<strong>Memory Group By</strong>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Spark
SQL</p></td>
-<td class="tableblock halign-left valign-top"><p
class="tableblock"><strong>Not supported</strong> as a first-class surface. You
cannot submit arbitrary Spark SQL / <code>DataFrame</code> queries from Hop
metadata; the engine only builds a Dataset graph from the Hop transform graph
(plus native handlers for a fixed set of transforms).</p></td>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><strong>Supported</strong> through the <a
href="../transforms/spark-sql.html" class="xref page">Spark SQL</a> transform:
it runs a <code>spark.sql</code> statement over the incoming Datasets, each
registered as a temporary view, and requires an explicit output field list.
Arbitrary <code>DataFrame</code> API code cannot be submitted from Hop
metadata.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">MLlib /
Spark ML</p></td>
diff --git a/manual/next/pipeline/transforms/abort.html
b/manual/next/pipeline/transforms/abort.html
index ae122d3423..a35ba42cfe 100644
--- a/manual/next/pipeline/transforms/abort.html
+++ b/manual/next/pipeline/transforms/abort.html
@@ -3148,6 +3148,14 @@
</tbody>
</table>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has <code>transforms/abort-basic.hpl</code>: a Filter
rows transform sends the row with <code>id</code> 4 to Abort, which stops the
pipeline with an error.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/accessoutput.html
b/manual/next/pipeline/transforms/accessoutput.html
index 11cbb4fb68..43f9d8eecb 100644
--- a/manual/next/pipeline/transforms/accessoutput.html
+++ b/manual/next/pipeline/transforms/accessoutput.html
@@ -3112,6 +3112,15 @@ Note: This name has to be unique in a single
pipeline.</p></td>
</tbody>
</table>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has
<code>transforms/microsoft-access-output.hpl</code>, which writes two rows from
a Data grid to a Microsoft Access file.
+Set the file name and the table name in the transform before you run it.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/addchecksum.html
b/manual/next/pipeline/transforms/addchecksum.html
index 66dd8e1e6f..437061eaa5 100644
--- a/manual/next/pipeline/transforms/addchecksum.html
+++ b/manual/next/pipeline/transforms/addchecksum.html
@@ -3171,6 +3171,24 @@ Note: You can use the "Get Fields" button to insert all
input fields from previo
</ul>
</div>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>transforms/add-a-checksum-CRC32.hpl</code>, which adds a CRC32
checksum of three fields to the rows of a Data grid.</p>
+</li>
+<li>
+<p><code>transforms/add-a-checksum-SHA-512.hpl</code>, which adds a
hexadecimal SHA-512 checksum of the same three fields.</p>
+</li>
+</ul>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/addconstant.html
b/manual/next/pipeline/transforms/addconstant.html
index 32f37a4016..53d20d490d 100644
--- a/manual/next/pipeline/transforms/addconstant.html
+++ b/manual/next/pipeline/transforms/addconstant.html
@@ -3203,6 +3203,14 @@ See <a href="../../concepts.html#data-types" class="xref
page">Data types</a>.</
</table>
</div>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has <code>transforms/add-constants.hpl</code>, which
adds a constant of each data type (BigNumber, Boolean, Date, Integer, Number,
String and Timestamp) to a generated row.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/addsequence.html
b/manual/next/pipeline/transforms/addsequence.html
index 68cf5fb9e4..a7b6bacc66 100644
--- a/manual/next/pipeline/transforms/addsequence.html
+++ b/manual/next/pipeline/transforms/addsequence.html
@@ -3175,6 +3175,24 @@ Avoids forcing unique sequencing across multiple
transforms.</p></td>
</tbody>
</table>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>transforms/add-sequence-unique-id.hpl</code>, which numbers 100
generated rows from 1 to 100 and writes the numbers to the log.</p>
+</li>
+<li>
+<p><code>transforms/add-sequence-cyclic-id.hpl</code>, which counts from 1 to
10 and then starts at 1 again, because the maximum value is 10.</p>
+</li>
+</ul>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/addxml.html
b/manual/next/pipeline/transforms/addxml.html
index 932c78ec5d..3e436d7b53 100644
--- a/manual/next/pipeline/transforms/addxml.html
+++ b/manual/next/pipeline/transforms/addxml.html
@@ -3406,6 +3406,14 @@ You want to turn the raw data into the database layout
below.</p>
</table>
</div>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has <code>transforms/add-xml-basic.hpl</code>, which
turns each Data grid row into a <code>row</code> XML element in the new field
<code>xmlvaluename</code>, with <code>group</code> as an attribute and the
other three fields as child elements.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/analyticquery.html
b/manual/next/pipeline/transforms/analyticquery.html
index e6ddf16392..3247c721de 100644
--- a/manual/next/pipeline/transforms/analyticquery.html
+++ b/manual/next/pipeline/transforms/analyticquery.html
@@ -3213,6 +3213,24 @@ bbb , 6 , 5</code></pre>
<p>Thus, by grouping (provided the input is sorted according to your
grouping), you can be assured that lead or lag operations will not return row
values outside of the defined group.</p>
</div>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>transforms/analyticquery-basic.hpl</code>, which adds the previous
and the next <code>desc</code> (LAG and LEAD) to each row.</p>
+</li>
+<li>
+<p><code>transforms/analyticquery-grouped.hpl</code>, which does the same
within each <code>id</code>.</p>
+</li>
+</ul>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/append.html
b/manual/next/pipeline/transforms/append.html
index 009707edad..7a810f0e72 100644
--- a/manual/next/pipeline/transforms/append.html
+++ b/manual/next/pipeline/transforms/append.html
@@ -3106,6 +3106,14 @@ Note: This name has to be unique in a single
pipeline.</p></td>
</tbody>
</table>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has <code>transforms/append-streams-basic.hpl</code>,
which sends the 10 rows of <strong>Second Stream</strong> (Head hop) and then
the 10 rows of <strong>First Stream</strong> (Tail hop) to one output.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/aws-sns-notify.html
b/manual/next/pipeline/transforms/aws-sns-notify.html
index 98400c55ec..58af3a2d09 100644
--- a/manual/next/pipeline/transforms/aws-sns-notify.html
+++ b/manual/next/pipeline/transforms/aws-sns-notify.html
@@ -3179,6 +3179,15 @@
</table>
</div>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has <code>transforms/aws-sns-notify.hpl</code>, which
sends one notification for the first row of a Data grid.
+Fill in the AWS credentials, the topic ARN, the subject and the message before
you run it.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/aws-sqs-reader.html
b/manual/next/pipeline/transforms/aws-sqs-reader.html
index 00e3b8c534..b9a7bbd57c 100644
--- a/manual/next/pipeline/transforms/aws-sqs-reader.html
+++ b/manual/next/pipeline/transforms/aws-sqs-reader.html
@@ -3189,6 +3189,15 @@
</div>
</div>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has <code>transforms/aws-sqs-reader.hpl</code>, which
reads messages from the <code>sample-queue</code> queue in
<code>eu-west-1</code>.
+It needs AWS credentials and an existing queue.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/azure-event-hubs-listener.html
b/manual/next/pipeline/transforms/azure-event-hubs-listener.html
index f949370853..74b553e71b 100644
--- a/manual/next/pipeline/transforms/azure-event-hubs-listener.html
+++ b/manual/next/pipeline/transforms/azure-event-hubs-listener.html
@@ -3209,6 +3209,15 @@ It receives the following fields:</p>
</ul>
</div>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has
<code>transforms/azure-event-hubs-listener.hpl</code>, which listens for
messages with the <code>$Default</code> consumer group.
+Fill in the Event Hubs connection settings before you run it.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/azure-event-hubs-writer.html
b/manual/next/pipeline/transforms/azure-event-hubs-writer.html
index 33f9e5599b..5539bdff7a 100644
--- a/manual/next/pipeline/transforms/azure-event-hubs-writer.html
+++ b/manual/next/pipeline/transforms/azure-event-hubs-writer.html
@@ -3100,6 +3100,15 @@ Please note you can use a transform like JSON Output or
"Java Script" to assembl
</ul>
</div>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has
<code>transforms/azure-event-hubs-writer.hpl</code>, which sends one event per
row of a Data grid to an event hub.
+Fill in the Event Hubs connection settings and choose <code>id</code> or
<code>name</code> as the Message field before you run it.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/blockingtransform.html
b/manual/next/pipeline/transforms/blockingtransform.html
index 8fdcec03d1..9f73251375 100644
--- a/manual/next/pipeline/transforms/blockingtransform.html
+++ b/manual/next/pipeline/transforms/blockingtransform.html
@@ -3134,6 +3134,14 @@ A new transform uses 1 - Fastest. A transform saved
before this option existed k
</tbody>
</table>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has
<code>transforms/blockingtransform-basic.hpl</code>, which generates 100,000
random UUIDs and passes them on only after the last one has arrived.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/blockuntiltransformsfinish.html
b/manual/next/pipeline/transforms/blockuntiltransformsfinish.html
index 8351ed9bf6..031de3b822 100644
--- a/manual/next/pipeline/transforms/blockuntiltransformsfinish.html
+++ b/manual/next/pipeline/transforms/blockuntiltransformsfinish.html
@@ -3126,6 +3126,15 @@ For the default number of copies (1), the CopyNr is
always 0.</p></td>
</tbody>
</table>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has
<code>transforms/block-until-transforms-finish-basic.hpl</code>: the row from
<strong>1 row</strong> waits until <strong>Found GOD!</strong> has finished
before it goes on to a JavaScript transform.
+<strong>Found GOD!</strong> gets 1,000 rows, each delayed by one second, so
the pipeline takes about 17 minutes.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/calculator.html
b/manual/next/pipeline/transforms/calculator.html
index da8776d733..9de89abab2 100644
--- a/manual/next/pipeline/transforms/calculator.html
+++ b/manual/next/pipeline/transforms/calculator.html
@@ -3835,6 +3835,24 @@ That is because Calculator takes data type of the left
hand size of the multipli
As such, if you want more precision, you should put field B on the left hand
side or change the data type to Number and all will be well.</p>
</div>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>transforms/calculator-basic.hpl</code>, which subtracts, adds,
multiplies and divides two numbers from a Data grid.</p>
+</li>
+<li>
+<p><code>transforms/calculator-jde-julian.hpl</code>, which converts dates to
JD Edwards Julian dates (CYYDDD) and back.</p>
+</li>
+</ul>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/calldbproc.html
b/manual/next/pipeline/transforms/calldbproc.html
index 4ce16c4480..bd93a59ee0 100644
--- a/manual/next/pipeline/transforms/calldbproc.html
+++ b/manual/next/pipeline/transforms/calldbproc.html
@@ -3212,6 +3212,15 @@
</table>
</div>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has <code>transforms/call-db-procedure.hpl</code>,
which calls H2’s built-in <code>LENGTH</code> function for two rows
through the <code>hop-samples</code> connection.
+To call a stored procedure of your own, change the connection and the
procedure name.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/changefileencoding.html
b/manual/next/pipeline/transforms/changefileencoding.html
index f393f539b7..82c3d75497 100644
--- a/manual/next/pipeline/transforms/changefileencoding.html
+++ b/manual/next/pipeline/transforms/changefileencoding.html
@@ -3117,6 +3117,14 @@
</ul>
</div>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has <code>transforms/change-file-encoding.hpl</code>,
which converts <code>files/change-file-encoding.txt</code> from UTF-8 to
ISO-8859-1 into <code>output/change-file-encoding.txt</code>.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/checkfilelocked.html
b/manual/next/pipeline/transforms/checkfilelocked.html
index 1ba14baac7..1c60e512ce 100644
--- a/manual/next/pipeline/transforms/checkfilelocked.html
+++ b/manual/next/pipeline/transforms/checkfilelocked.html
@@ -3089,6 +3089,14 @@
</ul>
</div>
</div>
+</div>
+<div class="sect1">
+<h2 id="_samples"><a class="link" href="#_samples">Samples</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The samples project has
<code>transforms/check-if-file-is-locked-basic.hpl</code>, which finds
<code>customers-100.txt</code> in the project, checks whether it is locked and
writes the result to the log.</p>
+</div>
+</div>
</div>
</article>
<nav class="pagination" data-pagefind-ignore aria-label="Page">
diff --git a/manual/next/pipeline/transforms/jsoninput.html
b/manual/next/pipeline/transforms/jsoninput.html
index 9adac857ef..b0a3cd53af 100644
--- a/manual/next/pipeline/transforms/jsoninput.html
+++ b/manual/next/pipeline/transforms/jsoninput.html
@@ -3558,6 +3558,24 @@ You can search for a field name by entering the field
name in the Search box.</p
<p>Click Select fields from snippet button and paste the entire JSON text and
it will populate the Name, Path, Type columns in the Fields tab. Example: This
is useful when copying JSON from a previous REST client’s output result.</p>
</div>
<div class="paragraph">
+<p><strong>Numbers</strong></p>
+</div>
+<div class="paragraph">
+<p>A JSON number, such as <code>199.5</code> or <code>12</code>, is read as
the number it is into an Integer, Number or BigNumber field. The Format,
Decimal and Group of the field are not used for it: they say how the field is
shown, and how a number that the JSON holds as a string, such as
<code>"1.234,50"</code>, is read. A number with decimals read into an Integer
field loses its fraction.</p>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+Before Hop 2.21, some JSON numbers were read with the Decimal and Group of the
field. Where the comma is the decimal symbol, set on the field or by the
locale, <code>199.5</code> could come out as <code>1995</code>.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
<p><strong>Dates and Timestamps</strong></p>
</div>
<div class="paragraph">
diff --git a/manual/next/pipeline/transforms/jsonnormalizeinput.html
b/manual/next/pipeline/transforms/jsonnormalizeinput.html
index 65435a6288..7f084d339d 100644
--- a/manual/next/pipeline/transforms/jsonnormalizeinput.html
+++ b/manual/next/pipeline/transforms/jsonnormalizeinput.html
@@ -3390,6 +3390,24 @@ You can search for a field name by entering it in the
Search box.</p>
<p>Click <strong>Select fields from snippet</strong> and paste JSON
text—typically <strong>one representative object</strong> (one element of the
array your <strong>Record JsonPath</strong> selects)—to populate the
<strong>Name</strong>, <strong>Path</strong>, and <strong>Type</strong> columns
in the Fields tab. This helps discover flattened paths after your Content-tab
settings (separator, depth, array handling) are applied.</p>
</div>
<div class="paragraph">
+<p><strong>Numbers</strong></p>
+</div>
+<div class="paragraph">
+<p>A JSON number, such as <code>199.5</code> or <code>12</code>, is read as
the number it is into an Integer, Number or BigNumber field. The Format,
Decimal and Group of the field are not used for it: they say how the field is
shown, and how a number that the JSON holds as a string, such as
<code>"1.234,50"</code>, is read. A number with decimals read into an Integer
field loses its fraction.</p>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+Before Hop 2.21, every JSON number was read with the Format, Decimal and Group
of the field. Where the comma is the decimal symbol, set on the field or by the
locale, <code>199.5</code> came out as <code>1995</code>.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
<p><strong>Dates and timestamps</strong></p>
</div>
<div class="paragraph">
diff --git a/manual/next/pipeline/transforms/pipeline-executor.html
b/manual/next/pipeline/transforms/pipeline-executor.html
index 3762814ec5..53717a2115 100644
--- a/manual/next/pipeline/transforms/pipeline-executor.html
+++ b/manual/next/pipeline/transforms/pipeline-executor.html
@@ -3206,7 +3206,8 @@ Click <strong>Open</strong> to open it in Hop Gui. When
the dialog has unsaved c
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Run
configuration</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Specify
the Pipeline Run Configuration to be used for execution.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Specify
the Pipeline Run Configuration to be used for execution.
+The transform reads the run configuration when it starts its first child
pipeline and uses it for every child pipeline that follows: a change to the run
configuration while the pipeline runs takes effect with the next run.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Stop after
(milliseconds)</p></td>
diff --git a/manual/next/pipeline/transforms/serialize-to-file.html
b/manual/next/pipeline/transforms/serialize-to-file.html
index 7284e5ff19..8610ae34b2 100644
--- a/manual/next/pipeline/transforms/serialize-to-file.html
+++ b/manual/next/pipeline/transforms/serialize-to-file.html
@@ -3113,6 +3113,13 @@ The metadata is stored in the file as well.</p>
<td class="tableblock halign-left valign-top"><p class="tableblock">Add
filenames to result</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Add the
written filename to the list of result filenames.</p></td>
</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p
class="tableblock">Compression level</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">How hard
to compress the file: 1 - Fastest, 2 - Very fast, 3 - Fast, 4 - Balanced,
faster, 5 - Balanced, 6 - Standard (the Java default), 7 - Smaller files, 8 -
Very small files, 9 - Smallest files.
+A low level writes much faster and gives a somewhat larger file.
+De-serialize from file reads every level.
+A new transform uses 6 - Standard, and so does a transform saved before this
option existed.</p></td>
+</tr>
</tbody>
</table>
</div>
diff --git a/manual/next/pipeline/transforms/zipfile.html
b/manual/next/pipeline/transforms/zipfile.html
index 278fc640bb..5ca3c71f43 100644
--- a/manual/next/pipeline/transforms/zipfile.html
+++ b/manual/next/pipeline/transforms/zipfile.html
@@ -3131,6 +3131,12 @@
<td class="tableblock halign-left valign-top"><p class="tableblock">Move to
folder fieldname</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Define the
field that contains the target folder to move the source file to after
zipping.</p></td>
</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p
class="tableblock">Compression level</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">How hard
to compress the files: 1 - Fastest, 2 - Very fast, 3 - Fast, 4 - Balanced,
faster, 5 - Balanced, 6 - Standard (the Java default), 7 - Smaller files, 8 -
Very small files, 9 - Smallest files.
+A lower level zips faster and gives a somewhat larger archive.
+A new transform uses 6 - Standard. A transform saved before this option
existed keeps 9 - Smallest files, the level it always used.</p></td>
+</tr>
</tbody>
</table>
</div>