You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hop.apache.org by gi...@apache.org on 2021/02/10 21:38:34 UTC

[incubator-hop-docs] branch asf-site updated: Documentation updated to 78713f3

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-hop-docs.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 6ba1ef9  Documentation updated to 78713f3
6ba1ef9 is described below

commit 6ba1ef9220270771e1e653f69544b1ab3ba20249
Author: jenkins <bu...@apache.org>
AuthorDate: Wed Feb 10 21:38:29 2021 +0000

    Documentation updated to 78713f3
---
 .../modules/ROOT/pages/plugins/transforms/combinationlookup.adoc      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/hop-user-manual/modules/ROOT/pages/plugins/transforms/combinationlookup.adoc b/hop-user-manual/modules/ROOT/pages/plugins/transforms/combinationlookup.adoc
index 6dfbdf0..6aeebc6 100644
--- a/hop-user-manual/modules/ROOT/pages/plugins/transforms/combinationlookup.adoc
+++ b/hop-user-manual/modules/ROOT/pages/plugins/transforms/combinationlookup.adoc
@@ -34,7 +34,7 @@ This transform creates/maintains a technical key out of data with business keys.
 
 This transform will maintain the key information only. You must update the non-key information in the dimension table, e.g. by putting an update transform (based on technical key) after the combination update/lookup transform.
 
-Project Hop will store the information in a table where the primary key is the combination of the business key fields in the table. Because this process can be slow if you have a large number of fields, a "hash code" field is supported that is representing all fields in the dimension. This can speed up lookup performance dramatically while limiting the fields to index to one field only.
+Apache Hop (Incubating) will store the information in a table where the primary key is the combination of the business key fields in the table. Because this process can be slow if you have a large number of fields, a "hash code" field is supported that is representing all fields in the dimension. This can speed up lookup performance dramatically while limiting the fields to index to one field only.
 
 == Options
 
@@ -63,4 +63,4 @@ A cache size of -1 means that caching is disabled.
 |Date of last update field|When required, specify the date of last update field (timestamp) from the source system to be copied to the data warehouse. For example, when you have an address without a primary key. The field will not be part of the lookup fields (nor be part in the hash code calculation). The value is written once only because any change results in a new record being written.
 |Get Fields button|Fills in all the available fields on the input stream, except for the keys you specified.
 |SQL button|Generates the SQL to build the dimension and allows you to execute this SQL. 
-|===
\ No newline at end of file
+|===