Snowflake Merge
Use this activity to run an SQL Merge statement on a Snowflake domain. The Snowflake Merge activity returns information in the form of rows affected.
Settings
The Settings tab has the following field:
Field | Description |
---|---|
Snowflake Connection | Name of the Snowflake connection. |
Input Settings
The Input Settings tab has the following fields:
Field | Description |
---|---|
Query |
An SQL statement used to merge a record in the table. You can construct prepared SQL queries by using substitution variables or parameters of the form Each substitution variable identifies an input parameter whose mapped value is substituted into the substitution variable at runtime. You can reuse the substitution variable for the same input parameter elsewhere in the query. The input fields on the Input tab of the activity are populated based on the SQL merge statement. You must include the semicolon (;) at the end of the query. To indicate the end of the merge query, a semicolon is expected at the end. A missing semicolon at the end causes the query to be unresponsive. Example of a merge query: For this merge query, id(INTEGER) is on the Input tab as this field is used as a parameter. Also, the mapped values for the id field are substituted into the id variable at runtime. |
Manually Configure Metadata | Set the Manually Configure Metadata field to true to fetch table metadata manually. For more information, see Using Manually Configure Metadata Option. |
Table Schema |
Displays the metadata of the SQL merge statement. You can modify the column metadata if Manually Configure Metadata is set to Note: If you modify the metadata, ensure that it agrees with the query added.
|
Input
The Input tab contains the input schema in a tree structure format. The fields that were selected in the Input Settings tab are available in the schema. You can either hard code their values or map them to a field from the output of a preceding activity in the flow by using the Mapper.
Output
The Output tab displays the output schema of the activity as a tree structure. The output is read-only. The properties that are displayed in the schema correspond to the output of this activity and can be used as input by subsequent activities in the flow.