This is an automated email from the ASF dual-hosted git repository.
hansva pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/hop.git
The following commit(s) were added to refs/heads/main by this push:
new 51bd5a7343 Fix typos in the user manual and remove a unit test log
message Hop no longer writes. #8902 (#8903)
51bd5a7343 is described below
commit 51bd5a734301e30d4951557fcc31d12e19202f30
Author: Adalennis <[email protected]>
AuthorDate: Wed Oct 14 09:36:57 2026 +0200
Fix typos in the user manual and remove a unit test log message Hop no
longer writes. #8902 (#8903)
---
.../ROOT/pages/hop-vs-kettle/import-kettle-projects.adoc | 2 +-
.../modules/ROOT/pages/pipeline/pipeline-unit-testing.adoc | 12 +++++-------
.../modules/ROOT/pages/pipeline/transforms/abort.adoc | 4 ++--
.../modules/ROOT/pages/pipeline/transforms/fake.adoc | 4 ++--
.../ROOT/pages/pipeline/transforms/getdatafromxml.adoc | 2 +-
.../modules/ROOT/pages/pipeline/transforms/jsoninput.adoc | 2 +-
.../modules/ROOT/pages/pipeline/transforms/ldapoutput.adoc | 2 +-
.../ROOT/pages/pipeline/transforms/pipeline-executor.adoc | 2 +-
.../ROOT/pages/pipeline/transforms/stringoperations.adoc | 2 +-
.../ROOT/pages/pipeline/transforms/textfileinput.adoc | 2 +-
.../modules/ROOT/pages/projects/advanced.adoc | 2 +-
.../modules/ROOT/pages/workflow/actions/graph-script.adoc | 2 +-
.../ROOT/pages/workflow/actions/processresultfilenames.adoc | 2 +-
13 files changed, 19 insertions(+), 21 deletions(-)
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/hop-vs-kettle/import-kettle-projects.adoc
b/docs/hop-user-manual/modules/ROOT/pages/hop-vs-kettle/import-kettle-projects.adoc
index 0047b6e588..9c4c45ed3d 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/hop-vs-kettle/import-kettle-projects.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/hop-vs-kettle/import-kettle-projects.adoc
@@ -18,7 +18,7 @@ under the License.
:imagesdir: ../assets/images
:page-pagination:
:page-pagination-no-next:
-:description: Compatibility with Kettle/PDI was never a goal for Apache Hop,
but since a lot of organizations have invested vast amounts of resources in
Kettle/PDI project development, the Apache Hop community provides a way to
import Kettle/PDI code into Hop and convert the imported code the the Hop ways
of working.
+:description: Compatibility with Kettle/PDI was never a goal for Apache Hop,
but since a lot of organizations have invested vast amounts of resources in
Kettle/PDI project development, the Apache Hop community provides a way to
import Kettle/PDI code into Hop and convert the imported code to the Hop ways
of working.
= Import Kettle (PDI) Projects in Apache Hop
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-unit-testing.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-unit-testing.adoc
index f87bdc6f3c..569a457a4d 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-unit-testing.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-unit-testing.adoc
@@ -202,10 +202,9 @@ If the pipeline runs with all tests passed, you'll receive
a notification in the
2025/04/02 21:16:43 - count by year.0 - Finished processing (I=0, O=0,
R=10000, W=22, U=0, E=0)
2025/04/02 21:16:43 - sort by year.0 - Finished processing (I=0, O=0, R=22,
W=22, U=0, E=0)
2025/04/02 21:16:43 - customers by year out.0 - Finished processing (I=0, O=0,
R=22, W=22, U=0, E=0)
-2025/04/02 21:16:43 - read-customers - Unit test 'read-customers UNIT' passed
succesfully
+2025/04/02 21:16:43 - read-customers - Unit test 'read-customers UNIT' passed
successfully
2025/04/02 21:16:43 - read-customers -
----------------------------------------------
-2025/04/02 21:16:43 - read-customers - customers by year out -
customers-by-year : Test passed succesfully against golden data set
-2025/04/02 21:16:43 - read-customers - Test passed succesfully against unit
test
+2025/04/02 21:16:43 - read-customers - customers by year out -
customers-by-year : Test passed successfully against golden data set
2025/04/02 21:16:43 - read-customers -
----------------------------------------------
2025/04/02 21:16:43 - read-customers - Pipeline duration : 0.108 seconds [
0.108 ]
2025/04/02 21:16:43 - read-customers - Execution finished on a local pipeline
engine with run configuration 'local'
@@ -217,7 +216,7 @@ In the example below, the number of rows for the year 1990
was changed from 486
image::pipeline-unit-testing-test-failed.png[Unit test - failed,width="90%"]
-While successful test show 'Test passed succesfully against golden data set'
and 'Test passed succesfully against unit test', failed unit tests may show one
of the error messages listed below:
+While successful tests show 'Test passed successfully against golden data
set', failed unit tests may show one of the error messages listed below:
* `Incorrect number of rows received from transform, golden data set
<GOLDEN_DATASET_NAME> has <GOLDEN_DATASET_ROWS> rows in it and we received
<NB_ROWS_FOUND>`
* `Validation against golden data failed for row number <ROW_NUMBER>, field
<FIELD_NAME>: transform value [<FIELD_VALUE>] does not correspond to data set
value [<GOLDEN_DATASET_VALUE>]`
@@ -261,10 +260,9 @@ In the workflow logging output, you'll find information
about the exit state of
[source,bash]
----
-2025/04/02 10:05:23 - read-customers - Unit test 'read-customers UNIT' passed
succesfully
+2025/04/02 10:05:23 - read-customers - Unit test 'read-customers UNIT' passed
successfully
2025/04/02 10:05:23 - read-customers -
----------------------------------------------
-2025/04/02 10:05:23 - read-customers - customers by year out -
customers-by-year : Test passed succesfully against golden data set
-2025/04/02 10:05:23 - read-customers - Test passed succesfully against unit
test
+2025/04/02 10:05:23 - read-customers - customers by year out -
customers-by-year : Test passed successfully against golden data set
2025/04/02 10:05:23 - read-customers -
----------------------------------------------
2025/04/02 10:05:23 - read-customers - Pipeline duration : 0.227 seconds [
0.227" ]
----
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/abort.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/abort.adoc
index 7de97ded44..bd824b2f9e 100644
--- a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/abort.adoc
+++ b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/abort.adoc
@@ -16,14 +16,14 @@ under the License.
////
:documentationPath: /pipeline/transforms/
:language: en_US
-:description: The Abort tranform aborts a running pipeline.
+:description: The Abort transform aborts a running pipeline.
:page-engines: Hop Engine=yes, Single Threaded=yes, Native Spark=yes, Beam
Spark=yes, Beam Flink=yes, Beam Dataflow=yes
= image:transforms/icons/abort.svg[Abort Icon, role="image-doc-icon"] Abort
== Description
-The Abort tranform aborts a running pipeline as soon as it receives input
data. The main use case for this transform is to throw an error when an
unexpected or unwanted situation occurs.
+The Abort transform aborts a running pipeline as soon as it receives input
data. The main use case for this transform is to throw an error when an
unexpected or unwanted situation occurs.
For example, you can use this transform so that a pipeline can be aborted
after x number of rows flow to over an error hop.
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/fake.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/fake.adoc
index feef0b64b6..77394859aa 100644
--- a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/fake.adoc
+++ b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/fake.adoc
@@ -16,14 +16,14 @@ under the License.
////
:documentationPath: /pipeline/transforms/
:language: en_US
-:description: The Fake Data tranform allows you to generate fake data using
the Java Faker library.
+:description: The Fake Data transform allows you to generate fake data using
the Java Faker library.
:page-engines: Hop Engine=yes, Single Threaded=yes, Native Spark=yes, Beam
Spark=yes, Beam Flink=yes, Beam Dataflow=yes
= image:transforms/icons/fake.svg[Fake data transform Icon,
role="image-doc-icon"] Fake data
== Description
-The Fake Data tranform allows you to generate fake data using the Java Faker
library (link:https://github.com/DiUS/java-faker[documentation]).
+The Fake Data transform allows you to generate fake data using the Java Faker
library (link:https://github.com/DiUS/java-faker[documentation]).
It can be used to generate pretty data for development, testing or showcasing
a project.
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/getdatafromxml.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/getdatafromxml.adoc
index 23eb9a946d..fd0fb78624 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/getdatafromxml.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/getdatafromxml.adoc
@@ -142,7 +142,7 @@ You can also do this using the
xref:pipeline/transforms/xmlinputstream.adoc[XML
|Type|The data type to convert to
|Format|The format or conversion mask to use in the data type conversion.
See xref:pipeline/formatting-values.adoc[Formatting numbers and dates].
-|Length|The maximum number of characters in the the output data value
+|Length|The maximum number of characters in the output data value
|Precision|The number of decimal places used to display numbers in the output
data
|Currency|The currency symbol to use for monetary values.
|Decimal|The numeric decimal symbol to use for floating-point numbers.
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/jsoninput.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/jsoninput.adoc
index 27f2529aa0..496db0829c 100644
--- a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/jsoninput.adoc
+++ b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/jsoninput.adoc
@@ -277,4 +277,4 @@ To change Hop's behavior regarding null values in JSON
files, so that null value
HOP_JSON_INPUT_INCLUDE_NULLS = N
----
-After restaring Hop, when we run the pipeline once again you will have 3 rows
resulting because the the null values will be omitted.
+After restarting Hop, when we run the pipeline once again you will have 3 rows
resulting because the null values will be omitted.
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/ldapoutput.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/ldapoutput.adoc
index 29d4598cc1..216c253ea9 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/ldapoutput.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/ldapoutput.adoc
@@ -69,7 +69,7 @@ The following sections describe the available options for the
LDAP Output transf
|===
|Option|Description
|Operation|Insert, Update, Upsert, Add attribute, Delete, Rename DN
(distinguished name), Remove attribute.
-|Multi valued field seperator|
+|Multi valued field separator|
|Fail if not exist|
|Dn fieldname|Field which contains the distinguished name.
|Old DN fieldname|Field which contains the old distinguished name (rename).
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/pipeline-executor.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/pipeline-executor.adoc
index 556b1c5cdb..f3a6c04d86 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/pipeline-executor.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/pipeline-executor.adoc
@@ -81,7 +81,7 @@ Samples (samples project):
|Pipeline a|Use this section to specify the pipeline to execute.
You have the following options to specify the pipeline:
-- Use a file for the pipeline: when this option is enabled, you can enter the
the .hpl file that is to be used as pipeline.
+- Use a file for the pipeline: when this option is enabled, you can enter the
.hpl file that is to be used as pipeline.
The filename may contain variables (for example, you can use the built-in
Internal.Pipeline.Filename.Directory variable to construct a filename relative
to the current pipeline), or you can use the "Browse" button to select a file
using a file browser.
|Pipeline from field?|Enable to specify the pipeline file name(s) in a field
in the input stream
|Pipeline field|When the previous option is enabled, you can specify the field
that will contain the pipeline filename(s) at runtime. The filename may contain
variables.
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/stringoperations.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/stringoperations.adoc
index 9b4cde2998..e54ae3db73 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/stringoperations.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/stringoperations.adoc
@@ -75,7 +75,7 @@ Values for Metadata Injection
1 = left +
2= right
|Pad Char| Character used for padding
-|Pad Length| Lenght to pad
+|Pad Length| Length to pad
|InitCap|0 = no +
1 = yes
|Escape|0 = none +
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/textfileinput.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/textfileinput.adoc
index be3ed4876d..cb756a54b9 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/textfileinput.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/textfileinput.adoc
@@ -109,7 +109,7 @@ For example, if your enclosure character is ' and you have
a field value 'six o'
Special characters (e.g. CHAR ASCII HEX01) can be set with the format
$[value], e.g. $[01] or $[6F,FF,00,1F].
|Allow breaks in enclosed fields?|If enabled, line breaks in enclosed fields
do not cause the field value to end. If disabled, or if the line break is in a
non-enclosed field, the field value ends at the line break, which can affect
the output of the transform. If you use the Get Fields button and one of the
fields ends because of a line break, that field is the last one recognized by
the Get fields function.
|Escape|Specify a character or characters that are used to identify characters
that should appear as-is in the field value when they might be interpreted as a
control or formatting character.
-For example, if you have \ as an escape character, the text 'Not the nine
o\'clock news' (where ' is the the enclosure character) gets parsed as Not the
nine o'clock news instead of splitting the field value.
+For example, if you have \ as an escape character, the text 'Not the nine
o\'clock news' (where ' is the enclosure character) gets parsed as Not the nine
o'clock news instead of splitting the field value.
Special characters (e.g. CHAR HEX01) can be set with the format $[value], e.g.
$[01] or $[6F,FF,00,1F].
The Escape character may be left empty, or set to the same character as the
Enclosure. In both cases a doubled enclosure inside an enclosed field (for
example "" when " is the enclosure) is treated as a single, literal enclosure
character and is de-duplicated in the resulting value, following the common CSV
convention (so "she said ""hi""" is read as she said "hi"). This also works
when "Allow breaks in enclosed fields?" is enabled.
|Return null for empty values which are not enclosed?|Enable to make a
difference between an empty value and a missing value. An empty value which is
not enclosed (`a;;b`) is then returned as null, while an empty enclosed value
(`a;"";b`) is returned as an empty string. A line ending on a separator
(`a;b;`) also returns null for that last value. When this option is disabled
(the default) both are handled the same way, as they always were. To keep the
difference between an empty string an [...]
diff --git a/docs/hop-user-manual/modules/ROOT/pages/projects/advanced.adoc
b/docs/hop-user-manual/modules/ROOT/pages/projects/advanced.adoc
index f63143b149..792558b2ca 100644
--- a/docs/hop-user-manual/modules/ROOT/pages/projects/advanced.adoc
+++ b/docs/hop-user-manual/modules/ROOT/pages/projects/advanced.adoc
@@ -146,7 +146,7 @@ See xref:projects/projects-environments.adoc[Projects and
Environments] for the
=== Environment configuration
-Hop enviroments and their home folders are stored in the hop configuration
file 'hop-config.json'.
+Hop environments and their home folders are stored in the hop configuration
file 'hop-config.json'.
That file lives by default in the *config* folder of the Hop installation.
System property `HOP_CONFIG_FOLDER` can also be used to point to a different
folder
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/workflow/actions/graph-script.adoc
b/docs/hop-user-manual/modules/ROOT/pages/workflow/actions/graph-script.adoc
index 1205f35e44..07aeafbe23 100644
--- a/docs/hop-user-manual/modules/ROOT/pages/workflow/actions/graph-script.adoc
+++ b/docs/hop-user-manual/modules/ROOT/pages/workflow/actions/graph-script.adoc
@@ -43,7 +43,7 @@ The result of this action is a `true` or `false` exit code
that determines if a
|The name of the connection on which you want to execute the cypher statements.
|Script
-|The script with cypher commands seperated by a semi-colon (;) on a new line.
+|The script with cypher commands separated by a semi-colon (;) on a new line.
For examples see below.
|Replace variables
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/workflow/actions/processresultfilenames.adoc
b/docs/hop-user-manual/modules/ROOT/pages/workflow/actions/processresultfilenames.adoc
index 0a6410738a..e99ef62531 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/workflow/actions/processresultfilenames.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/workflow/actions/processresultfilenames.adoc
@@ -39,7 +39,7 @@ The `Process result filenames` action allows you to copy,
move or delete a numbe
|Create destination folder|use this option to create the destination folder
when it does not exist
|Replace existing file|use this option to overwrite existing files
|Remove source filenames from result|use this option to remove the processed
filenames from the list of result filenames
-|Add destination filenames to result|use this option to add the the processed
target filenames to the list of result filenames
+|Add destination filenames to result|use this option to add the processed
target filenames to the list of result filenames
|Add date to filename|add the date to the target filename, e.g. yyyyMMdd
|Add time to filename|add the time to the target filename, e.g. HHmmss
|Specify date time format|allows you to specify your own date-time format,
e.g. yyyyMMdd_HHmmss
