Filter Rows
Options
Option | Description |
---|---|
Transform name | Optionally, you can change the name of this transform to fit your needs. |
Send 'true' data to transform | The rows for which the condition specified is true are sent to this transform |
Send 'false' data to transform | The rows for which the condition specified are false are sent to this transform |
The Condition | |
Add Condition | Click to add conditions. Add condition converts the original condition into a sub-level condition. Click a sub-condition to edit it by going down one level in the condition tree. |
Filtering
Filtering rows based on values from variables
The filter rows transform detects only fields in the input stream. If you want to filter rows based on a variable value, you must modify the previous transform (a table input for example) and include the variable as another field, for example:
${myvar}=5
A query:
SELECT field1,
field2,
${myvar} AS field3
FROM table
WHERE field1=xxxx
Then in the filter row condition, you can have
field1 = field3
FYI - instead of the Table Input trick above you can use the simple "Get Variables" transform to set parameters in fields.
Metadata injection support
All fields of this transform support metadata injection. You can use this transform with ETL Metadata Injection to pass metadata to your pipeline at runtime.
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 .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:
-
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.
-
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.
-
Find the <condition> element and its nested elements and modify it accordingly to use it in your MDI scenario.