In this article
Overview
You can use this Snap to execute a SQL UPDATE statement for each batch of input documents. Keys from the document are used as the columns to update and their values will be the updated value in the column.
Updates will be batched up until the account's batch size property or until the structure of the update statement changes. An UPDATE statement will change if an incoming document contains different keys than a previous document.
This Snap also supports DML (Data Manipulation Language) operations (ALTER and INSERT) when using the AWS Athena database.
Snap Type
Snowflake Update is a Write-type Snap that executes SQL SELECT statement.
Prerequisites
None.
Support for Ultra Pipelines
Works in Ultra Pipelines. However, we recommend that you not use this Snap in an Ultra Pipeline. This operation is not supported for Apache Hive databases.
Known Issues & Limitations
None.
Snap Views
Type | Format | Number of views | Examples of Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document |
|
| This Snap has exactly one document input view. |
Output | Document |
|
| This Snap has at most one document output view. If an output view is available, then the original document that was used to create the statement will be output with the status of the update. |
Error | Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter while running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab. The available options are:
Learn more about Error handling in Pipelines. |
Snap Settings
Asterisk (*): Indicates a mandatory field.
Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.
Expression icon (): Indicates whether the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.
Add icon (): Indicates that you can add fields in the field set.
Remove icon (): Indicates that you can remove fields from the field set.
Field Name | Field Type | Description |
---|---|---|
Label* Default Value: Generic JDBC - Update | String | Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline. |
Schema Name Default Value: N/A | String/Expression | Specify the database schema name. In case it is not defined, then the suggestion for the Table Name will retrieve all tables names of all schemas. The property is suggestible and will retrieve available database schemas during suggest values. The values can be passed using the pipeline parameters but not the upstream parameter. |
Table Name* Default Value: N/A | String/Expression | Specify the name of the table in the instance. The table name is suggestible and requires an account setting. The values can be passed using the pipeline parameters but not the upstream parameter. |
Update Condition Default Value: N/A Macro lookup error: excerpt "ME_DB_Snaps_Query_Examples" was not found on page "Oracle - Update" (with ID 1438908) in space "SD". If you're experiencing issues please see our Troubleshooting Guide. | String/Expression | Specify the SQL WHERE clause of the update statement. |
Number of retries Default Value: 0 | Integer/Expression | Specify the maximum number of attempts to be made to receive a response. The request is terminated if the attempts do not result in a response. |
Retry interval (seconds) Default Value: 1 | Integer/Expression | Specify the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception. |
Snap Execution Default Value: Execute only | Dropdown list | Select one of the three modes in which the Snap executes. Available options are:
|
Examples
Updating data in an SQL database
This example pipeline demonstrates how to update the data in the SQL database.
Step 1: Configure the Mapper Snap to pass the data. On validation, the Snap displays the output based on the specified input.
Step 2: Configure the Generic JDBC - Update Snap to update the “TECTONIC”.”ACTRESS1” table with the update condition. On validation, the Snap displays a confirmation message indicating that the data was successfully updated in the database.
Downloads
Release | Snap Pack Version | Date | Type | Updates |
---|---|---|---|---|
November 2024 | main29029 |
| Stable | Updated and certified against the current SnapLogic Platform release. |
August 2024 | 438patches28541 |
| Latest | The JDBC Snap Pack version
|
August 2024 | 438patches28052 |
| Latest | Fixed a connectivity issue with the Generic JDBC Snaps that resulted in an error when attempting to connect the JDBC account to a Sybase database using the Breaking change: Your existing pipelines that use JDBC Snaps to integrate with Oracle or Redshift databases using the bundled Oracle or Redshift JDBC drivers will stop functioning with the 438patches28052. |
August 2024 | main27765 | Stable | Updated and certified against the current Snaplogic Platform release. | |
May 2024 | 437patches27416 |
| Latest | Fixed an issue with the Generic JDBC—Insert Snap that exposed sensitive information in the error message when the batch operation was not successful. |
May 2024 | main26341 | Stable | Updated and certified against the current SnapLogic Platform release. | |
February 2024 | 436patches25244 |
| Latest |
|
February 2024 | main25112 |
| Stable | Added the following new Snaps to the JDBC Snap Pack:
|
November 2023 | 435patches24781 |
| Latest | The database connection error message in the Generic Database Account is improved for clarity and readability. |
November 2023 | main23721 |
| Stable | Updated and certified against the current SnapLogic Platform release. |
August 2023 | main22460 |
| Stable | Updated and certified against the current SnapLogic Platform release. |
May 2023 | main21015 |
| Stable | The Generic Database Account now supports the SSH Tunneling connection. You can now encrypt the network connection between your client and the database server, ensuring a highly secure connection. |
February 2023 | main19844 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
November 2022 | main18944 |
| Stable | The Generic JDBC - Insert Snap previously took a longer time to execute and was aborted after a few minutes, which affected the performance of the Snap. The Snap's performance is optimized now and takes lesser time for execution. |
September 2022 | 430patches17894 |
| Latest | The Generic JDBC Snaps connecting to the DB2 database now take lesser time to execute thereby improving the performance. |
August 2022 | main17386 |
| Stable | Enhanced the Generic Database account Support dynamic values for Account, Advanced, and URL properties. |
4.29 Patch | 429patches16588 |
| Latest |
|
4.29 | main15993 |
| Stable | Enhanced the Generic Database Account in the JDBC Snap pack to include Netsuite as an option for the Database name field to connect to the NetSuite database. While configuring the account, if you select Netsuite or Autodetect (if the Snap detects the target database as NetSuite) then the Limit rows field in the Generic JDBC - Select Snap is ignored. |
4.28 | main14627 |
| Stable | Enhanced the following Snaps to support DML (Data Manipulation Language) operations (CREATE, ALTER, INSERT, and SELECT) when using AWS Athena database. |
4.27 | main12833 |
| Stable |
|
4.26 | main11181 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.25 Patch | 425patches11008 |
| Latest |
|
4.25 | main9554 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.24 Patch | 4.24patches8903 |
| Latest | Fixes the Pipeline execution failure issue when using the JDBC Snaps with a Microsoft Access account by setting the correct quotation handler for the configured account. |
4.24 | main8556 | Stable | Enhances the Generic JDBC - Select Snap to return only the fields (provided in the Output Fields) in the output schema (second output view), through a new check box Fetch Output Fields In Schema. If the Output Fields property is empty all the columns are visible. | |
4.23 Patch | 423patches8027 |
| Latest | Fixes the multiple connection issue in the JDBC Snap Pack that occurs when the Auto Detect field is enabled for each execution of the Snap by storing a copy of the database name. |
4.23 Patch | 423patches7800 |
| Latest | Fixes an issue with JDBC account through a Test Query option that establishes a database connection upon using Auto detect option for the Database name. |
4.23 | main7430 |
| Stable |
|
4.22 Patch | 422patches7246 |
| Latest | Fixes the file descriptor error in the Snap Pack by removing logging exception which was causing log file spam. |
4.22 Patch | 422patches6772 |
| Latest | Fixes the issue with |
4.22 | main6403 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.21 Patch | 421patches6272 |
| Latest | Fixes the issue where Snowflake SCD2 Snap generates two output documents despite no changes to Cause-historization fields with DATE, TIME and TIMESTAMP Snowflake data types, and with Ignore unchanged rows field selected. |
4.21 Patch | 421patches6144 |
| Latest | Fixes the following issues with DB Snaps:
|
4.21 Patch | MULTIPLE8841 |
| Latest | Fixes the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends. |
4.21 | snapsmrc542 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.20 Patch | jdbc8783 |
| Latest | Fixes the Generic JDBC Execute Snap that adds the value of the previous column's field to a NULL field when SELECT queries having duplicate column names are run on the PostgreSQL database. |
4.20 | snapsmrc535 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.19 Patch | db/jdbc8405 |
| Latest | Fixes an issue with the Generic JDBC - Update Snap wherein the Snap is unable to perform operations when:
|
4.19 | snaprsmrc528 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.18 | snapsmrc523 |
| Stable | Added support for JDBC account Active Directory authentication for SQL server for driver JAR version |
4.17 | ALL7402 |
| Latest | Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers. |
4.17 | snapsmrc515 |
| Latest |
|
4.16 Patch | MULTIPLE7123 |
| Latest | Added two new properties, Number of retries and Retry interval, to Execute, Insert, Select, and Update Snaps that enables you to handle retry attempts during a connection failure. |
4.16 | snapsmrc508 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.15 | snapsmrc500 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.14 | snapsmrc490 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.13 Patch | jdbc5231 |
| Latest | Added binding information for DB2 database connection on the Generic JDBC Snap Pack to ensure that pipelines correctly validate and execute. |
4.13 Patch | jdbc5229 |
| Latest | Added test connection query for SQLMX database in the JDBC Accounts to check if the database connection is valid. |
4.13 | snapsmrc486 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.12 Patch | MULTIPLE4744 |
| Latest | Added support to execute multiple queries in a single batch for Snowflake, this patch affects Generic JDBC Execute. |
4.12 | snapsmrc480 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.11 | snapsmrc465 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.10 | snapsmrc414 |
| Stable | Adds Auto commit property to the Select and Execute Snaps at the Snap level to support overriding of the Auto commit property at the Account level. |
4.9.0 Patch | jdbc3242 |
| Latest | Addresses an issue in JDBC Execute Snap with functions not working (fixes by executing commit() at the end of the processing query). |
4.9.0 Patch | jdbc3205 |
| Latest | Fixes auto-commit issue for PostgreSQL SELECT query. |
4.9.0 Patch | jdbc3133 |
| Latest | Fixed error handling of the limit clause by adding Apache Derby support. |
4.9.0 Patch | jdbc3069 |
| Latest | Fixed an issue regarding connection not closed after login failure; Expose autocommit for "Select into" statement in PostgreSQL Execute Snap and Redshift Execute Snap. |
4.9 | snapsmrc405 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.8.0 Patch | jdbc2801 |
| Latest | Addressed an issue with Generic JDBC - Execute Snap holding the resultset in memory, exhausting memory and causing a core dump. |
4.8.0 Patch | jdbc2753 |
| Latest | Potential fix for JDBC deadlock issue. |
4.8 | snapsmrc398 |
| Stable |
|
4.7 Patch | jdbc2195 |
| Latest | Fixed an issue for database Select Snaps regarding Limit rows not supporting an empty string from a pipeline parameter. |
4.7 | snapsmrc382 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.6 | snapsmrc362 |
| Stable |
Known Issue:
|
4.5.1 | snapsmrc344 |
| Stable | Resolved an issue with JDBC Select failing with a syntax error when special characters were used. |
4.5 | snapsmrc344 |
| Stable |
|
4.4.1 | N/A |
| Stable |
|
4.4 | N/A |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.3.2 | N/A |
| Stable | Resolved an issue with Generic JDBC Update updating null into database when an invalid string value is provided as input for time datatype. |
4.3.1 | N/A | N/A | Stable |
|
4.2.2 | N/A | N/A | Stable |
|
4.2.1 | N/A | N/A | Stable |
|
Related Content