You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hop.apache.org by ha...@apache.org on 2023/10/13 12:57:04 UTC
[hop] branch master updated: Update getvariable.adoc
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 c3062a0488 Update getvariable.adoc
new 41c38e1768 Merge pull request #3226 from Mattang-Dan/patch-15
c3062a0488 is described below
commit c3062a048831aa9197956af88ce3226c0f1a7ee5
Author: Mattang-Dan <10...@users.noreply.github.com>
AuthorDate: Thu Sep 14 05:17:17 2023 -0700
Update getvariable.adoc
Fixed formatting
---
.../ROOT/pages/pipeline/transforms/getvariable.adoc | 16 ++++++----------
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/getvariable.adoc b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/getvariable.adoc
index 06452e13f4..01abaa913d 100644
--- a/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/getvariable.adoc
+++ b/docs/hop-user-manual/modules/ROOT/pages/pipeline/transforms/getvariable.adoc
@@ -29,22 +29,18 @@ under the License.
The Get Variables transform allows you to get the value of a variable and create field(s) from it or allows you to add values to existing input rows. You could consider it to be a "Set fields” transform. It can retrieve the value of a previous variable and/or retrieves previous rows or you can set static values to a variable or input rows. You only need to use this transform if you need the variable value in a field.
-
Note that workflow/environment variables are set only once. A pipeline needs to start to get any new variables. A running or sequential or nested (nested pipelines are technically the same pipeline) pipeline can't fetch new variable values. A pipeline is considered started when a pipeline starts for every row in a pipeline executor.
+You can always refer to variables/parameters using the syntax: ${myVariable}, for example from a previous pipeline.
-You can always refer to variables/parameters using the syntax: ${myVariable}, for example from a previous pipeline.
-
-
-For example, you can specify: ${openvar}java.io.tmpdir{closevar}/hop/tempfile.txt and it will be expanded to /tmp/hop/tempfile.txt on Unix-like systems.
+For example, you can specify: ``${openvar}java.io.tmpdir{closevar}/hop/tempfile.txt`` and it will be expanded to ``/tmp/hop/tempfile.txt`` on Unix-like systems.
You must always specify the data type or you will have errors like the following:
-'''
- 2023/07/21 09:30:23 - REST client.0 - ERROR: Because of an error, this transform can't continue:
- 2023/07/21 09:30:23 - REST client.0 - TOKEN_URL None : Unknown type 0 specified.
- 2023/07/21 09:30:23 - REST client.0 - ERROR: org.apache.hop.core.exception.HopValueException:
-'''
+
+``2023/07/21 09:30:23 - REST client.0 - ERROR: Because of an error, this transform can't continue:
+ 2023/07/21 09:30:23 - REST client.0 - TOKEN_URL None : Unknown type 0 specified.
+ 2023/07/21 09:30:23 - REST client.0 - ERROR: org.apache.hop.core.exception.HopValueException:``
See also the Set Variables transform.
To convert the Variable into a data type other than String use Select Values - Meta Data tab.