This is an automated email from the ASF dual-hosted git repository.
hansva pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hop.git
The following commit(s) were added to refs/heads/master by this push:
new 6e84a06799 Update writetolog.adoc
new 2bc2042dc6 Merge pull request #3467 from Mattang-Dan/patch-58
6e84a06799 is described below
commit 6e84a06799925b7d32d5d765a3e59b78a3d3cce9
Author: Mattang-Dan <[email protected]>
AuthorDate: Wed Nov 29 06:52:44 2023 -0800
Update writetolog.adoc
---
.../ROOT/pages/pipeline/transforms/writetolog.adoc | 26 ++++++++++++----------
1 file changed, 14 insertions(+), 12 deletions(-)
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/writetolog.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/writetolog.adoc
index c740e8c901..eeb351db98 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/writetolog.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/writetolog.adoc
@@ -31,18 +31,6 @@ The Write To Log transform writes information to the Hop
logging system.
Typical use cases are logging specific values or custom logging messages to
the Hop logs.
-TIP: be careful when writing variables or fields for (unencrypted) passwords
or other sensitive information to the Hop logging system!
-
-If no fields are specified it will write out all fields to the log. If at
least one field is specified it will only print out that field. Parameters and
variables must be specified in the Log message section.
-
-A Logging level must be set. Set the Log detail level to Basic if you want
variables to be printed out.
-
-Example to print a parameter or variable in the Log Message section:
``COUNTER: ${openvar}COUNTER${closevar}``
-
-If no fields exist, you will have to use a "Generate rows" transform to create
a dummy row in order to print variables or parameters.
-
-TIP: If an error stops anything from being written to the log, then disable
the Hops that fail, and add logging just before the failure, and re-run
-
|
== Supported Engines
[%noheader,cols="2,1a",frame=none, role="table-supported-engines"]
@@ -54,6 +42,20 @@ TIP: If an error stops anything from being written to the
log, then disable the
!===
|===
+== Usage
+
+TIP: Be careful when writing variables or fields for (unencrypted) passwords
or other sensitive information to the Hop logging system!
+
+If no fields are added in the Write to log Fields list, it will write out all
fields to the log if a Basic Log level is specified. If fields are added to
Fields list it will only print out those field(s). Parameters and variables
must be specified in the Log message section.
+
+A Logging level must be set. Set the Log detail level to Basic if you want
variables to be printed out.
+
+Example to print a parameter or variable in the Log Message section:
``COUNTER: ${myCounter}``
+
+If a data row does not exist containing fields, logging fields, parameters, or
variables will not work. You may use a "Generate rows" transform to create a
dummy row in order to print variables or parameters.
+
+TIP: If an error stops anything from being written to the log, then disable
the Hops that fail, and add logging just before the failure, and re-run.
+
== Options
[options="header"]
