Skip to end of banner
Go to start of banner

Generic JDBC - Update

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 40 Next »

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

Generic JDBC - Update is a Write-type Snap that executes SQL UPDATE 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

  • Min: 1

  • Max: 1

  • Mapper

  • Sequence

This Snap has exactly one document input view.

Output

Document

  • Min: 0

  • Max: 1

  • File Writer

  • Mapper

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:

  • Stop Pipeline Execution: Stops the current pipeline execution when the Snap encounters an error.

  • Discard Error Data and Continue: Ignores the error, discards that record, and continues with the rest of the records.

  • Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Snap Settings

  • Asterisk (*): Indicates a mandatory field.

  • Suggestion icon ((blue star)): Indicates a list that is dynamically populated based on the configuration.

  • Expression icon ((blue star)): Indicates whether the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Add icon ((blue star)): Indicates that you can add fields in the field set.

  • Remove icon ((blue star)): Indicates that you can remove fields from the field set.

Field Name

Field Type

Description

Label*

Default ValueGeneric JDBC - Update
ExampleGeneric 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
Example: "PUBLIC"

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
Example: Employee

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
Example:

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. You can define specific values or columns to update (Set condition) in the upstream Snap, such as Mapper Snap, and then use the WHERE clause to apply these conditions on the columns sourced from the upstream Snap. For instance, here is a sample of an Update SQL query:
UPDATE table_name
SET column1 = value1, column2 = value2,
WHERE condition;

If the Update Condition field is left blank, the condition is applied on all the records of the target table. 

Refer to the example to understand how to use the Update Condition.

Number of retries

Default Value: 0
Example: 3

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
Example: 10

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
ExampleValidate & Execute

Dropdown list

Select one of the three modes in which the Snap executes. Available options are:

  • Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.

  • Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.

  • Disabled: Disables the Snap and all Snaps that are downstream from it.

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

  1. Download and import the Pipeline into SnapLogic.

  2. Configure Snap accounts as applicable.

  3. Provide Pipeline parameters as applicable.

  File Modified
No files shared here yet.

Snap Pack History

 Click here to expand...

Release 

Snap Pack Version

Date

Type

  Updates

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 jConnect driver.

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.
Workaround
You must manually upload the Oracle or Redshift JDBC driver in the JDBC Database account to run your pipelines successfully.
Download the drivers:
OJDBC: Maven Repository: com.oracle.database.jdbc » ojdbc6 » 11.2.0.4
Redshift: Maven Repository: com.amazon.redshift » redshift-jdbc42 » 2.1.0.11

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

  • Fixed an issue with the Generic JDBC-Select, Insert, Update, and Table List Snaps that incorrectly displayed the Schema Name suggestions with the Cassandra driver connection.

  • Fixed an issue with the Generic JDBC-Select Snap that displayed an empty result with the MariaDB driver connection for output 1.

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

  • Fixed an issue with JDBC Select and JDBC Insert Snaps where the Snaps did not load suggestions for the Table property. Now the Snaps load the suggestions correctly.

  • Enhanced the Generic Database account to support dynamic values for Account properties, Advanced properties, and URL properties so that you can pass these values through Pipeline parameters.

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

  • Fixed an issue with Generic JDBC - Select Snap where if there are URL properties in the account, the unPooledConnection does not use the properties when creating a connection. This causes the auto-detect functionality to use the wrong database name.

  • Fixed an issue with MySQL and MariaDB in Generic JDBC - Update Snap when a table is incorrectly reported as not being found.

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

  • Fixes an issue with the JDBC account that displays a connection is closed error when connecting with the SQL server.

  • Fixes an issue with the JDBC Snaps that fail while displaying the javax.management.MalformedObjectNameException: Invalid character '=' in value part of property error repeatedly when there is “=“ or ”:” in the JDBC URL connection.

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 Auto detect in Generic JDBC - Execute Snap by implementing the JDBC Auto detect feature to use the correct database name.

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:

  • The connection thread waits indefinitely causing the subsequent connection requests to become unresponsive.

  • Connection leaks occur during Pipeline execution.

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:

  • An expression is used in the Update condition property.

  • Input data contain the character '?'.

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 mssql-jdbc-6.2.2-jre8.jar.

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

  • Fixes an issue with the Generic JDBC Execute Snap wherein the Snap would send the input document to the output view even if the Pass through field is not selected in the Snap configuration. With this fix, the Snap sends the input document to the output view, under the key original, only if you select the Pass through field.

  • Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during preview check box.

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

  • Updated the default value for the property Min pool size to 0. 

  • Info tab added to accounts.

  • Database accounts now invalidate connection pools if account properties are modified and login attempts fail.

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

  • Enhanced Generic JDBC Execute Snap to fully support SQL statements with/without expressions & SQL bind variables.

  • Resolved an issue in Generic JDBC Insert Snap that caused unexpectedly failures on Snowflake and connecting to DB2.

  • Resolved an issue in Generic JDBC Select Snap that caused errors with Teradata database instance.

  • Resolved an issue in Generic JDBC Select Snap with Snowflake account that caused an error when auto-commit was not selected.

  • Resolved an issue in Generic JDBC Select Snap with Snowflake account that caused an error when a merge statement was used in the Snap.

Known Issue:

  • JDBC Insert: "The Maximum Possible Row Length in the Table is too Large" error message: You will see this message if trying to insert data into Teradata that is larger than Teradata can handle (rows are limited to approximately 64,000 bytes). Workaround: Use smaller default column size, e.g., 32000 bytes.

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

  • Verified Generic JDBC Snaps connections to Hive. See JDBC Account for configuration information. SELECT and INSERT are supported. SnapLogic does not support UPDATE, DELETE, or MERGE due to limitations in the drivers. 

  • Resolved an issue in Generic JDBC Insert Snap that occurred when inserting records in batches. 

  • Resolved an issue in Generic JDBC Insert Snap that occurred because of an SQL execution (internal) error.

  • Resolved an issue in Generic JDBC Select Snap that occurred because of an SQL query execution. 

4.4.1

N/A

 

Stable

  • Added expression support to the Where clause property for Select Snaps.

  • Resolved an issue with the JDBC Select Snap failing with Teradata because of a Limit Offset.

  • Resolved an issue with JDBC Execute failing to execute a create or replace table statement with Snowflake.

  • Resolved issues with JDBC Insert Snap:

    • Failing to create a table when Create table if not present is selected.

    • An exception occurred when attempting to insert record containing date columns into Teradata.

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

  • New! Generic JDBC SELECT Snap

  • New! Generic JDBC UPDATE Snap

  • Feature: JDBC Snaps - add a new property 'Database name' to JDBC Account

  • Defect: JDBC Execute Snap fails in preview for Oracle timestamp data type

  • Defect: JDBC Insert to Snowflake throws an error

  • Defect: Generic JDBC Execute with JDBC4OLAP drivers to connect to Essbase resulted in com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Unable to parse content type: null

4.2.2

N/A

N/A

Stable

  • Ignore empty result added to Execute Snap. The option will not write any document to the output view for select statements producing no results.

  • Addressed an issue with idle timeouts.

  • Resolved an issue in JDBC Execute throwing an exception, unable to get driver.

4.2.1

N/A

N/A

Stable

  • Resolved Generic JDBC Execute not working with value substitution.

  • Resolved JDBC Execute unable to read CLOB columns via jTDS/JDBC.


Related Content

  • No labels