Enhanced the following Snaps to support DML (Data Manipulation Language) operations (CREATE, ALTER, INSERT, and SELECT) when using AWS Athena database.

• Generic JDBC - Execute

• Generic JDBC - Insert

• Generic JDBC - Select

• Enhanced the Generic JDBC Database Account to skip batch execution, when the Batch size value is one. When the Batch size is greater than one, the batch is executed.
• Enhanced the Generic JDBC - Execute Snap to invoke stored procedures.

• 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.

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.

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.

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

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.

• 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.

Fixes the file descriptor error in the Snap Pack by removing logging exception which was causing log file spam.

Fixes the issue with Auto detect in Generic JDBC - Execute Snap by implementing the JDBC Auto detect feature to use the correct database name.

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.

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.

Fixes the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends.

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.

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 '?'.

Added support for JDBC account Active Directory authentication for SQL server for driver JAR version mssql-jdbc-6.2.2-jre8.jar.

Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.

• 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.

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.

Added binding information for DB2 database connection on the Generic JDBC Snap Pack to ensure that pipelines correctly validate and execute.   

Added test connection query for SQLMX database in the JDBC Accounts to check if the database connection is valid.

snapsmrc486

Added support to execute multiple queries in a single batch for Snowflake, this patch affects Generic JDBC Execute. 

snapsmrc480

snapsmrc414

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.

Addresses an issue in JDBC Execute Snap with functions not working (fixes by executing commit() at the end of the processing query).

Fixes auto-commit issue for PostgreSQL SELECT query.

Fixed error handling of the limit clause by adding Apache Derby support.

Fixed an issue regarding connection not closed after login failure; Expose autocommit for "Select into" statement in PostgreSQL Execute Snap and Redshift Execute Snap.

Addressed an issue with Generic JDBC - Execute Snap holding the resultset in memory, exhausting memory and causing a core dump.

Potential fix for JDBC deadlock issue.

snapsmrc398

• 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.

Fixed an issue for database Select Snaps regarding Limit rows not supporting an empty string from a pipeline parameter.

snapsmrc382

• 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.

snapsmrc344

Resolved an issue with JDBC Select failing with a syntax error when special characters were used.

snapsmrc344

• 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. 

• 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.

Resolved an issue with Generic JDBC Update updating null into database when an invalid string value is provided as input for time datatype.

• 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

• 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.

• Resolved Generic JDBC Execute not working with value substitution.

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