I have confirmed that it is the Snowflake API that is doing this and the output component has no control over this. Thank you for investigating. I will look at the API Spec, & may end up contacting Snowflake to see if this behavior can be controlled thru the API. Until then, I will control this behavior by creating a joblet without the component.
@mhodent ,when you were trying to load data into main table,is it creating a first temp table and loading to temp first and then loading to main table ?
@mhodent ,the attachment is export of the code ? if yes i am getting error like There is no valid items to import, and make sure the selected path contain valid items.
no, that was a export > generate HTML Doc.. unzip and look at the design.
the problem is that the tdboutput generates a temp table as an intermediary step (on snowflake instance), and I would like to bypass creating the temp table & have the output just do a put, then a load directly to my target table
@mhodent ,useally we will not specify any temp table in talend job,may be that will create in snowflake and need to check the snowflake settings? can you show me where it was creating?
when I use the tdboutput to push the file into snowflake, I can see that a temp table is created for before the insert statement when looking at query history within snowflake history interface.
