4.24 (main8614) - 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 - 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 - 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) 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 - Fixes the file descriptor error in the Snap Pack by removing logging exception which was causing log file spam.
4.22 422patches6772 - 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) 4.21 Patch 421patches6272 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 - 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 - Fixes the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends.
4.21 (snapsmrc542) 4.20 Patch jdbc8783 - 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) 4.19 Patch db/jdbc8405 - 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 (snapsmrc528) 4.18 (snapsmrc523) - Added support for JDBC account Active Directory authentication for SQL server for driver JAR version
mssql-jdbc-6.2.2-jre8.jar .
4.17 Patch ALL7402 - Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.
4.17 (snapsmrc515) - 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 - 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) - No updates made. Automatic rebuild with a platform release.
4.15 (snapsmrc500) - No updates made. Automatic rebuild with a platform release.
4.14 (snapsmrc490) - No updates made. Automatic rebuild with a platform release.
4.13 Patch jdbc5231 - 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 - Added test connection query for SQLMX database in the JDBC Accounts to check if the database connection is valid.
4.13 (snapsmrc486) - No updates made. Automatic rebuild with a platform release.
4.12 Patch MULTIPLE4744 - Added support to execute multiple queries in a single batch for Snowflake, this patch affects Generic JDBC Execute.
4.12 (snapsmrc480) - No updates made. Automatic rebuild with a platform release.
4.11 (snapsmrc465) - No updates made. Automatic rebuild with a platform release.
4.10 (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.
4.9.0 Patch jdbc3242 - 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 - Fixes auto-commit issue for PostgreSQL SELECT query
4.9.0 Patch db/jdbc3133 - Error in handling the limit clause has been fixed by adding Apache Derby support
4.9.0 Patch jdbc3069 - Fixes 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) - No updates made. Automatic rebuild with a platform release.
4.8.0 Patch jdbc2801 - 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 - Potential fix for JDBC deadlock issue.
4.8 (snapsmrc398) 4.7 Patch jdbc2195 4.6 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.
Info |
---|
| 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 4.5.0 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.0 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:
4.3.2 4.3.1 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 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 June 27, 2015 (2015.22) - JDBC Execute Snap: SQL operation failed with an invalid batch command when using table name as an input variable.
- JSON paths in WHERE clauses should be processed as bind values after the expression is evaluated.
June 6, 2015 (2015.20) - JDBC Insert Snap fails to insert joda LocalTime object to PosgreSQL TIME data type
- Dynamic DB queries now supported in the Execute Snap.
The SQL statement property now can be set as an expression property. When it is an expression, it will be evaluated with each input document and one SQL statement per each input document will be executed.
Info |
---|
| When the SQL statement property is an expression, the pipeline parameters are shown in the suggest, but not the input schema. |
Warning |
---|
With the SQL statement property set as an expression, the Snap can be exposed to SQL injection. Please use this feature with caution. |
October 18, 2014 August 2013 |