...
NOTE this operator ignores lhub_scores in the joins, and if lhub_scores are present in the nodes except root step they will get dropped. Renaming lhub_scores would keep them in the playbook
Operator Usage in Easy Mode
- Click + on the parent node.
- Enter the Auto Join Tables operator in the search field and select the operator from the Results to open the operator form.
- In the Table drop-down, enter or select a table or list of tables to join.
- Optional. In the Result Tables drop-down, select a table or list of tables, whose additional columns will be added to the first table and the rest will be dropped.
- Click Run to view the result.
- Click Save to add the operator to the playbook.
- Click Cancel to discard the operator form.
Usage Details
LQL Command
Code Block |
---|
autoJoinTables([list of steps (tables)],)s-- join all steps and collect all new columns autoJoinTables([list of steps (tables)], list of desired steps in the output) -- join all steps and in the output show only the columns from the second list of step |
Note
When second list is empty, it will join all in sequential order and collect all new columns so output will contain all columns from all tables, if second list is not empty then it will still perform sequential join but in the output it will show only the columns from the second list of step, for better understandin look at the examples below.
Example
Input
table1:
Node name | columns |
---|---|
NodeA | a, b, c |
NodeB | b, c, d |
NodeC | c, d, e |
NodeD | d, e, f |
NodeE | e, f, g |
...