Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
krajew4
Contributor
Contributor

@guenneguez jeremy​ 

 

I understand what you mean and I think the idea is correct but ~:> in my case I am doing an iteration on top level, each iteration migrates one table. I can't set properties for UPDATE and INSERT and MERGE ON on tSQLTemplateMerge before I run the job - I only know which columns I want to migrate once the job is running.

 

In the meantime I found SQL Templates in Talend Studio and analyzed Merge Update, Merge Insert and Snowflake Merge templates. From what I understood given how tSQLTemplateMerge component it needs to have properties set before you run the job.

 

I am using now tDBOutput for Snowflake and I am providing the schema in form of dynamic variable prepared in Java code one step before. The merge generated but tDBOutput (table action set to UPSERT) should be generated by that Snowflake Merge template as I understood. This template iterates on:

 

__UPDATE_MAPPING_SRC_COLUMN__

__INSERT_MAPPING_TRG_COLUMN__

 

to prepare list of columns for UPDATE MATCHED and INSERT NOT MATCHED unfortunately there is no way to set the name of the template for tDBOutput for snowflake and no way to change the internals of this component so I am stuck with black box behaviour I cannot modify.