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/01/07 16:36:12 UTC
[incubator-hop-docs] branch asf-site updated: Documentation updated
to 560c339
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 d1497b8 Documentation updated to 560c339
d1497b8 is described below
commit d1497b846b4f7addb5be3f33dabbeb6b85a526e0
Author: jenkins <bu...@apache.org>
AuthorDate: Thu Jan 7 16:36:06 2021 +0000
Documentation updated to 560c339
---
hop-user-manual/modules/ROOT/pages/plugins/transforms/filterrows.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hop-user-manual/modules/ROOT/pages/plugins/transforms/filterrows.adoc b/hop-user-manual/modules/ROOT/pages/plugins/transforms/filterrows.adoc
index d78feb6..f1f5afe 100644
--- a/hop-user-manual/modules/ROOT/pages/plugins/transforms/filterrows.adoc
+++ b/hop-user-manual/modules/ROOT/pages/plugins/transforms/filterrows.adoc
@@ -78,10 +78,10 @@ All fields of this transform support metadata injection. You can use this transf
== Special considerations for the condition field
-The Filter Rows transform is a special MDI scenario, since it has a nested structure of filter conditions. The condition is given in XML format. The condition XML has the same format as we store the pipeline metadata in a .KTR file in XML format. We do not have a DTD (Document Type Definition) for the .KTR XML format, nor the condition.
+The Filter Rows transform is a special MDI scenario, since it has a nested structure of filter conditions. The condition is given in XML format. The condition XML has the same format as we store the pipeline metadata in a .HPL file in XML format. We do not have a DTD (Document Type Definition) for the .HPL XML format, nor the condition.
It is easy to get to an XML condition:
1. Create a sample Filter transform with the different conditions you need. This sample transform gives you all the information, such as the values for the functions you use.
-2. Select the transform, copy it to the clipboard, and then paste it into a text editor. Alternatively, you can store the .KTR, and then open the .KTR in a text editor.
+2. Select the transform, copy it to the clipboard, and then paste it into a text editor. Alternatively, you can store the .HPL, and then open the .HPL in a text editor.
3. Find the <condition> element and its nested elements and modify it accordingly to use it in your MDI scenario.