Skip to end of banner
Go to start of banner

Snowflake Account

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 41 Next »

On this Page

 

This account is used by Snaps in the Snowflake Snap Pack.

You can create an account from SnapLogic Designer or Manager. In Designer, when working on pipelines, every Snap that needs an account prompts you to create a new account or use an existing account. The accounts can be created in or used from:

  • Your private project folder: This folder contains the pipelines that will use the account.
  • Your Project Space’s shared folder: This folder is accessible to all the users that belong to the Project Space.
  • The global shared folder: This folder is accessible to all the users within an organization in the SnapLogic instance.

Account Configuration

In Manager, you can navigate to the required folder and create an account in it (see Accounts). To create an account for Snowflake: 

  1. Click Create, then select Snowflake > Snowflake S3 Database Account or Snowflake > Snowflake S3 Dynamic Account or Snowflake Azure Database Account.
  2. Supply an account label.
  3. Supply the Account properties and Advanced properties for your Snowflake Database account. When using Snowflake S3 Dynamic Account, you can specify the Account properties as expressions referencing pipeline parameters.
  4. (Optional) Supply additional information on this account in the Notes field of the Info tab.
  5. Click Apply.

Avoid changing account credentials while pipelines using them are in progress. This may lead to unexpected results, including locking the account.


If the Snap fails to connect to the database, it will retry three more times. 

You can Validate an account connection when creating a Snowflake S3 Database Account but not when creating a Snowflake S3 Dynamic Account because the account properties of a dynamic account are provided dynamically as pipeline parameters.

The difference between Snowflake S3 Database Account and Snowflake S3 Dynamic Account is that in the latter you can specify the Account properties as expressions referencing pipeline parameters. For information on setting up a Snowflake Dynamic Account, see Using Pipeline Parameters in Account Configuration, below.

For details on account encryption, see Using Account Encryption, below.

Account Types

Snowflake Azure Database Account

 Account Settings

You can use the Snowflake Azure Account option to create both standard and dynamic accounts. If you want to enter a dynamic value for a specific field, click the '=' button adjacent to the concerned field, and you can use expressions in the field to specify dynamic values as required.

Account Settings

Label


Required. The name for the account.

Default value: None.

Account properties

Required. The information required to create the account.

JDBC jars


Required. The list of JDBC jars to be loaded (Snowflake JDBC jar 3.0.0 or higher).

The Snowflake account has been tested for version 3.6.17 JDBC jar.

Example: snowflake-jdbc-3.6.17.jar

Default value: None.

Hostname


Required. The hostname of the Snowflake server to which you want to connect the new account.

Example: demo.snowflake.net

Default value: None.

Port Number


Required. The port number associated with the Snowflake database server that you want to use for this account.

Default value: 443 

Username


The username that you want to use to connect to the database server.

Example: testuser

Default value: None. 

Password


The password associated with the username specified above. This will be used as the default password while retrieving connections.

Default value: None.

Database name


Required. The name of the database to which you want to connect.

Example: testdb

Default value: None.

Warehouse name


Required. The name of the warehouse to which you want to connect.

Example: testwh

Default value: None.

JBDC Driver Class

The fully-qualified name of the JDBC driver class to be used for connecting to the server.

Example: net.snowflake.client.jdbc.SnowflakeDriver

Default value: com.snowflake.client.jdbc.SnowflakeDriver

Azure storage account name


The name of the instance of the Azure storage account.

Example: testazurestorage

Default value: None.

Azure storage account key


The key needed to connect to the instance of the Azure storage account listed above.

You can use either of the two keys available in the Access Key tab of the dashboard in the Azure portal to populate this value.

Default value: None.

Container


The name of the Azure storage blob container that you want to use for hosting files.

Example: Container1

Default value: None.

Path


The location of the folder in the container listed above where you want to host files.

Example: Folder1/SubFolder1

Default value: None.

Shared Access Token Signature Method

The method of supplying the SAS token to the Snaps. You can choose between the following two options:

  • User Supplied: Choose this option if you intend to manually enter the shared access token signature.

    If you opt for the User Supplied option, then you need to ensure that your tokens are valid whenever the pipeline is run; else, the pipelines will fail. For more information, see Generating a SAS Token in Snowflake documentation.

  • System Generated: Choose this option if you want Snaps to generate and use the SAS tokens as and when required.

Default value: User Supplied

User token

The shared access token that you want to use to access the Azure storage blob folder specified in the Path above. You can get a valid SAS token from the Azure portal.

This property is applicable only when you choose User Supplied in the Shared Access Token Signature Method field above. 

Default value: None.

Client side encryption

Allows the Snaps to encrypt the blob before being uploaded to Microsoft Azure. You can choose between the following two options:

  • None: Indicates that you do not want to use client-side encryption.
  • Custom_Key: Indicates that you want to use a custom key to access the storage blob.

Default value: None.

Custom key

The custom key that you want to use to access the Azure storage blob.

This property is applicable only when you select Custom_Key in the Client side encryption field above. The key should be a 128- or 256-bit Base64-encoded key.

Default value: None.

Advanced properties

URL Properties

Use these fields to configure the URLs associated with this account.

URL property name


The name of the URL property.

Default value: None.

Example: queryTimeout

URL property value


The URL property value associated with the URL property name.

Default value: None.

Example: 0

Batch size


Required. The number of statements that you want to execute at a time.

Select queries are not batched.

Using a large batch size could use up the JDBC placeholder limit of 2100.

Default value: 50

Fetch size


Required. The number of rows you want a query to fetch during each execution.

Large values could cause the server to run out of memory.

 Default value: 100

Min pool size


Required. The minimum number of idle connections that you want the pool to maintain at a time. 

Default value: 3

Minimum value: 0

Maximum value: No limit

Max pool size


Required. The maximum number of connections that you want the pool to maintain at a time.

Snowflake Bulk Load/Bulk Upsert/S3 Upsert Snap requires a minimum of 2 connections per Snap in a pipeline. For example, if a pipeline has a Snowflake Bulk Load Snap and an S3 Upsert Snap, then the pool size must be greater than or equal to 4 for successful execution.

Default value: 50

Minimum value: 0

Maximum value: No limit

Max life time


Required. The maximum lifetime of a connection in the pool. Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit. A value of 0 indicates an infinite lifetime, subject to the Idle Timeout value. An in-use connection is never retired. Connections are removed only after they are closed.

Default value: 60

Idle Timeout


Required. The maximum amount of time a connection is allowed to sit idle in the pool. A value of 0 indicates that idle connections are never removed from the pool.

Default value: 5

Checkout timeout


Required. The number of milliseconds you want the system to wait for a connection to become available when the pool is exhausted. A value of 0 instructs the system to wait forever. For any other value, the system throws an exception after the wait time has expired.

Default value: 10000

Snowflake S3 Database Account

 Account Settings

Label


Required. The name for the account.

Default value: None.

Account propertiesEnter the details in the subsequent fields that will create a connection to the S3 database.
JDBC JARs

Required. The JDBC JAR files to be loaded (Snowflake JDBC jar 3.0.0 or higher). Click the + button at the right of the field to add a row.

The Snowflake account has been tested for version 3.6.17 JDBC JAR.

Example: snowflake-jdbc-3.6.17.jar

Default value: None.

Hostname

Required. The hostname of the Snowflake server to which you want to connect.

Example: demo.snowflake.net

Default value: None.

Port Number

Required. The port number associated with the Snowflake S3 database server that you want to use for this account.

Example: 808

Default value: 443

Username

The username that you want to use to connect to the Snowflake database server.

Example: testuser

Default value: None.

Password

The password for the username specified in Username. This password is used as the default password while retrieving connections.

Default value: None.

Database name

Required. The name of the Snowflake database to which you want to connect.

Example: testdb

Default value: None.

Warehouse name

Required. The name of the warehouse to which you want to connect.

Example: testwh

Default value: None.

JBDC Driver Class

The fully-qualified/domain name of the JDBC driver class to be used for connecting to the server.

Example: net.snowflake.client.jdbc.SnowflakeDriver

Default value: com.snowflake.client.jdbc.SnowflakeDriver

S3 Bucket


Required only when using an external staging location. The name of the S3 bucket that you want to use for staging data to Snowflake. 

  • S3 bucket is mandatory for Snowflake Bulk Load and Unload Snaps.
  • For optimal performance, this S3 bucket should be located in the same AWS region as the Snowflake instance.

Example: sl-bucket-ca

Default value: None.

S3 Folder


Required only when using an external staging location. The relative path to a folder in the S3 bucket listed in the S3 Bucket field. This is used as a root folder for staging data to Snowflake.

S3 Folder is mandatory for Snowflake Bulk Load and Unload Snaps.

Example: https://sl-bucket-ca.s3.<ca>.amazonaws/<sf>

Default value: None

S3 Access-key ID


Required only when using an external staging location. The S3 access key ID that you want to use for AWS authentication.

S3 Access-key ID is mandatory for Snowflake Bulk Load and Unload Snaps.

Example: NAVRGGRV7EDCFVLKJH

Default value: None

S3 Secret key


Required only when using an external staging location. The S3 secret key associated with the S3 Access-ID key listed in the S3 Access-key ID field.

S3 Access-key ID is mandatory for Snowflake Bulk Load and Unload Snaps.

Example: 2RGiLmL/6bCujkKLaRuUJHY9uSDEjNYr+ozHRtg

Default value: None

Advanced properties

URL Properties

Use these fields to configure the URLs associated with this account.

URL property name


The name of the URL property. URL property is the full URL.

Default value: None.

Example: queryTimeout

URL property value


The URL property value associated with the URL property name.

Default value: None.

Example: 0

Batch size


Required. The number of Snowflake queries that you want to execute at a time.

  • Select queries are not batched.
  • Using a large batch size could use up the JDBC placeholder limit of 2100.

Default value: 50

Example: 8

Fetch size


RequiredThe number of rows a query must fetch for each execution.

Large values could cause the server to run out of memory.

Default value: 100

Example: 12

Min pool size


Required. The minimum number of idle connections that you want the pool to maintain at a time. 

Default value: 3

Minimum value: 0

Maximum value: No limit

Max pool size


Required. The maximum number of connections that you want the pool to maintain at a time.

Default value: 15

Minimum value: 0

Maximum value: No limit

Max life time

Required. The maximum lifetime of a connection in the pool, in seconds.   

  • Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit.
  • 0 indicates an infinite lifetime, subject to the Idle Timeout value.
  • An in-use connection is never retired. Connections are removed only after they are closed.

Default value: 60

Minimum value: 0

Maximum value: No limit

Idle Timeout


Required. The maximum amount of time in seconds that a connection is allowed to sit idle in the pool. 

0 indicates that idle connections are never removed from the pool.

Default value: 5

Minimum value: 0

Maximum value: No limit

Checkout timeout


Required. The maximum time in milliseconds you want the system to wait for a connection to become available when the pool is exhausted.

0 instructs the system to wait forever. For any other value, the system throws an exception after the wait time.

Default value: 10000

Minimum value: 0

Maximum value: No limit

Snowflake S3 Dynamic Account

 Account Settings

Label


Required. The name for the account.

Default value: None.

Account properties

Required. The information required to create a connection to the database.

JDBC jars


Required. The list of JDBC jars to be loaded (Snowflake JDBC jar 3.0.0 or higher). Click the + button at the right of the field to add a row.

The Snowflake account has been tested for version 3.6.17 JDBC jar.

Example: snowflake-jdbc-3.6.17.jar

Default value: None.

Hostname


Required. The hostname of the Snowflake server to which you want to connect for the new account.

Example: demo.snowflake.net

Default value: None.

Port Number


Required. The port number associated with the Snowflake database server that you want to use for this account.

Default value: 443

Username


The username that you want to use to connect to the database server.

Example: testuser

Default value: None.

Password


The password associated with the username specified above. This will be used as the default password while retrieving connections.

Default value: None.

Database name


Required. The name of the database to which you want to connect.

Example: testdb

Default value: None.

Warehouse name


Required. The name of the warehouse to which you want to connect.

Example: testwh

Default value: None.

JBDC Driver Class

The fully-qualified name of the driver class to be used for connecting to the server.

Example: net.snowflake.client.jdbc.SnowflakeDriver

Default value: com.snowflake.client.jdbc.SnowflakeDriver

S3 Bucket


Required only when using an external staging location. The S3 bucket that you want to use for staging data onto Snowflake. 

The field is required when using the Bulk Load and Unload Snaps. For optimal performance, this S3 bucket should be located in the same AWS region as the snowflake instance.

 Default value: None.

S3 Folder


Required only when using an external staging location. Relative path to a folder in the S3 Bucket listed in the S3 Bucket field. This is used as a root folder for staging data onto Snowflake.

The field is required when using the Snowflake Bulk Load and Unload Snaps.

Default value: None.

S3 Access-key ID


Required only when using an external staging location. The S3 access key ID that you want to use for AWS authentication.

The field is required when using the Snowflake Bulk Load and Unload Snaps.

 Default value: None.

S3 Secret key


Required only when using an external staging location. The S3 secret key associated with the S3 Access-ID key listed in the field above.

The field is required when using the Snowflake Bulk Load and Unload Snaps.

 Default value: None.

Advanced properties

URL Properties

Use these fields to configure the URLs associated with this account.

URL property name


The name of the URL property.

Default value: None.

Example: queryTimeout

URL property value


The URL property value associated with the URL property name.

Default value: None.

Example: 0

Batch size


Required. The number of statements that you want to execute at a time.

Select queries are not batched.

Using a large batch size could use up the JDBC placeholder limit of 2100.

Default value: 50


Fetch size


RequiredThe number of rows you want a query to fetch during each execution.

 Large values could cause the server to run out of memory.

 Default value: 100

Min pool size


Required. The minimum number of idle connections that you want the pool to maintain at a time. 

Default value: 3

Minimum value: 0

Maximum value: No limit

Max pool size


Required. The maximum number of connections that you want the pool to maintain at a time.

Default value: 15

Minimum value: 0

Maximum value: No limit

Max life time

Required. Maximum lifetime of a connection in the pool. Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit. A value of 0 indicates an infinite lifetime, subject to the Idle Timeout value. An in-use connection is never retired. Connections are removed only after they are closed.

Default value: 60

Idle Timeout


Required. The maximum amount of time a connection is allowed to sit idle in the pool. A value of 0 indicates that idle connections are never removed from the pool.

Default value: 5

Checkout timeout


Required. The number of milliseconds you want the system to wait for a connection to become available when the pool is exhausted. A value of 0 instructs the system to wait forever. For any other value, the system throws an exception after the wait time has expired.

Default value: 10000

Using Account Encryption

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.

Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.

Account

  • High: Password
  • Medium + High: Username, password
  • Low + Medium + High: Username, password

Using Pipeline Parameters in Account Configuration

You can use pipeline parameters when configuring dynamic Snowflake accounts. For information on pipeline parameters, see Pipeline Parameters in Pipeline Properties.

Example

Define the following two pipeline parameters in the pipeline with which you want to associate the new account:

  • User_name
  • Pass_word

You will use these values in the dynamic account.

Back in the Snowflake pipeline, create a Snowflake Dynamic Account 

  • Set the expression toggle on for both Username and Password
  • Set Username to _user_name and Password to _password
  • Click Apply and fill the Snap Settings for the desired function.
You cannot Validate an account connection when creating a Snowflake Dynamic Account because the account properties of a dynamic account are provided dynamically as pipeline parameters.


Apply the changes. Your dynamic account is now configured; and your username and password details should change as you update them in your pipeline parameters.


See Also

Release 

Snap Pack Version

Date

Type

  Updates

November 2024

main29029

Stable

Updated and certified against the current SnapLogic Platform release.

August 2024

438patches28811

Latest

Fixed an issue with the Snowflake Snaps where the Snaps intermittently displayed an error requesting to rollback/commit.

August 2024

438patches28667

Latest

Added the Snowflake - Snowpipe Streaming Snap that enables data insertion into Snowflake using the Snowpipe Streaming API. It allows for continuous data ingestion into Snowflake tables as soon as data becomes available.

August 2024

main27765

Stable

Upgraded the org.json.json library from v20090211 to v20240303, which is fully backward compatible.

May 2024

437patches27531

Latest

Enhanced the Snowflake - Select Snap with Time Travel query support that enables you to access historical data at any point within a defined period. This includes restoring data-related objects, duplicating and backing up data, and analyzing data usage.

May 2024

437patches27156

Latest

May 2024

437patches26821

Latest

  • Added Snowflake - Vector Search Snap to enable advanced vector-based queries as part of the Select statement.

  • Enhanced the Snowflake Snap Pack with full vector support, including schema generation and output compatibility with vector data types.

May 2024

437patches26508

Latest

May 2024

main26341

Stable

  • Enhanced the Snowflake Bulk Load and Snowflake Insert Snaps to support iceberg tables. Iceberg tables partition and organize data across multiple nodes to distribute the workload and speed up data processing.

  • Updated the Delete Condition (Truncates a Table if empty) field in the Snowflake - Delete Snap to Delete condition (deletes all records from a table if left blank) to indicate that all entries will be deleted from the table when this field is blank, but no truncate operation is performed.

February 2024

436patches25630

Latest

  • Enhanced the Snowflake Bulk Load Snap to fetch the file format types based on the selected Datasource. The Snap now supports only CSV and NONE file format types (as a Suggestions list) when the Datasource is Input view.

  • Enhanced the Snowflake Bulk Upsert Snap to support only CSV and NONE file format types (as a Suggestions list).

February 2024

main25112

Stable

Updated and certified against the current SnapLogic Platform release.

November 2023

435patches24865

Latest

Fixed an issue across the Snowflake Snaps that populated all suggestions for the Schema and Table Names existing in the configured Snowflake Account. Now, the Snaps only populate suggestions related to the database configured in the Account.

November 2023

435patches24110

Latest

Added a lint warning to the Snowflake-Bulk Load Snap that recommends users to select the Purge checkbox when the Data source is input view and the Staging location is External.

November 2023

main23721

Stable

The Snowflake Snap Pack is now bundled with the default Snowflake JDBC driver v3.14.

August 2023

434patches23541

Latest

Fixed an issue with the Snowflake-Bulk Load Snap where the Snap wrote irrelevant errors to the error view when both of the following conditions occurred:

  • The inserted data was not in the same order as the table schema.

  •  The Staging location was Internal.

Now, the Snap  writes the correct errors to the error view.

August 2023

main22460

Stable

The Snowflake - Execute Snap now includes a new Query type field. When Auto is selected, the Snap tries to determine the query type automatically.

May 2023

433patches21890

Latest

  • Enhanced the Snowflake - Bulk Load and Snowflake - Bulk Upsert Snaps with a new Flush chunk size (in bytes) field. When using internal staging, data is written to a temporary chunk file. When the file exceeds the specified size, it is copied to the Snowflake stage and deleted.

  • Added validation of external storage credentials for Snowflake S3 Accounts.

May 2023

433patches21370

Latest

  • Fixed an issue where the output document was missing information about the error records count and the reason for the error.

  • Fixed an issue that caused stored procedure executions to fail in the Snowflake - Multi Execute Snap.

May 2023

main21015

Stable

  • Snaplogic is specified as a partner tag in all requests going to Snowflake, making it easier for Snowflake to identify the requests coming from Snaplogic.

  • The default JDBC driver JAR for the Snowflake Snap Pack is upgraded to version 3.13.28 to support the GEOMETRY data type.

February 2023

432patches20906

Latest

  • The default JDBC driver JAR for the Snowflake Snap Pack is upgraded to version 3.13.28 to support the GEOMETRY data type.

  • Fixed an issue with the Snowflake Multi Execute Snap to enable processing of large amounts of data (more than 2 billion records).

  • Fixed a column mismatch issue that was caused by an assumed null AWS token that could potentially be an empty string.

February 2023

432patches20266

Latest

Fixed an issue with the Snowflake - Bulk Load Snap that resulted in lowercase (or mixed case) column names when creating a new table under specific conditions. The new Create table with uppercase column names checkbox addresses this issue.

February 2023

432patches20120

 

Latest

The Snowflake Bulk Load, Bulk Upsert, and Unload Snaps now support expressions for the Staging location field.

February 2023

main19844

 

Stable

  • The JDBC Driver (JAR file) setting in all the Snowflake Accounts is optional. If you do not provide a JDBC driver, the account uses the default Snowflake JDBC driver JAR V3.13.25 that is bundled with the Snap Pack.

November 2022

431patches19581

 

Latest

  • The Snowflake SCD2 Snap works as expected and does not display the Cannot find input data related to the output record error when you use the TIMESTAMPNTZ data type columns as Natural key fields.

  • Fixed the memory leakage issue ( because of Key/pair authentication that occupied some memory)  in the Snowflake Snaps. The performance of the Snowflake Snaps is optimized—there is less memory consumption, and exact memory dumps before and after the Pipeline execution.

November 2022

431patches19454

 

Latest

The Snowflake Snap Pack supports geospatial data types. As the Snowflake Snap Pack requires using our custom Snowflake JDBC driver for full support of all data types, contact support@snaplogic.com for details.

November 2022

431patches19220

 

Latest

The Snowflake S3 OAuth2 Account now support expressions for external staging fields.

November 2022

431patches19220

 

Latest

  • The Snowflake - Bulk Upsert Snap no longer supports values from an upstream input document in the Key columns field when the expression button is enabled. The value must remain constant throughout the Snap’s execution and now limits support for expressions to include only Pipeline parameters.

    To avoid breaking your existing Pipelines that use a value from the input schema in the Key columns field, update the Snap settings to use an input value from Pipeline parameters instead.

  • The Snowflake Bulk Load Snap no longer displays the validation warning in the following cases:

    • When you configure the Validation Mode as NONE and Validation Errors Type as Do not show errors in the Snap, or

    • When Validation Mode is RETURN_n_ROWS, RETURN_ERRORS, or RETURN_ALL_ERRORS.

November 2022

main18944

 

Stable

  • The Snowflake - Bulk Load Snap now routes the 403-Access Denied error to the error view (when the error view is enabled) when you do not have DeleteObject permission to delete the temporary files in the S3 bucket.

  • Fixed the following issues in the Snowflake - Bulk Load Snap:

    • The Snap failed when the Preserve case sensitivity field was not selected and the column names in the input document and the target table were the same but the cases were different. Now, the Snap does not fail and loads the data correctly to the target table.

    • The Snap created a table when it did not exist with multiple columns in the target table when there were two input views, but the column name cases were different in both views. Now, the Snap creates the table from the metadata provided by the second input view and loads the data into the target table from the first input view.

  • The Snowflake Insert Snap now creates the target table only from the table metadata of the second input view when the following conditions are met:

    • The Create table if not present checkbox is selected.

    • The target table does not exist.

    • The table metadata is provided in the second input view.

November 2022

430patches18911

 

Latest

Because of performance issues, all Snowflake Snaps now ignore the Cancel queued queries when pipeline is stopped or if it fails option for Manage Queued Queries, even when selected. Snaps behave as though the default Continue to execute queued queries when the Pipeline is stopped or if it fails option were selected.

October 2022

430patches18781

 

Latest

The Snowflake Insert and Snowflake Bulk Upsert Snaps now do not fail with the SQL Operation failed error, when you insert the uppercase key name into a mixed-case column if the Preserve case sensitivity checkbox is deselected.

The Snowflake Bulk Load Snap now works as expected when you configure On Error with SKIP_FILE_*error_percent_limit*% and set the Error Percent Limit to more than the percentage of rows with invalid data in the CSV file.

October 2022

430patches18432

 

Latest

The Snowflake Bulk Load Snap now has a Validation Errors Type dynamic field, which provides options for displaying validation errors. You can now choose Aggregate errors per row to display a summary view of errors.

September 2022

430patches17962

 

Latest

The Snowflake Bulk Load Snap now triggers the metadata query only once even for invalid input, thereby improving the performance of Snap.

September 2022

430patches17894

 

Latest

The Snowflake Select Snap now works as expected when the table name is dependent on an upstream input.

August 2022

430patches17748

 

Latest

Fixes in the Snowflake Bulk Load Snap:

  • The Snap now routes the 403-Access Denied error to the error view (when the error view is enabled) when you do not have DeleteObject permission to delete the temporary files in the S3 bucket.

  • The Snap now checks for the expiration time whenever it receives a new access token for refreshing the token in Snowflake OAuth2 account.

August 2022

430patches17377

 

Latest

  • The following issues are fixed in the Snowflake - Bulk Load Snap:

    • The Snap successfully loads the data even when you deselect the Preserve case- sensitivity checkbox and the source and target column names are similar, but with different casing.

    • When the Snap has two input views, it creates the target table from the metadata provided by the second input view and loads the data into the target table from the first input view.

  • The Snowflake Select Snap now validates successfully even when you set the Table Name field with an expression.

August 2022

main17386

 

Stable

The following Snowflake Accounts support Key Pair Authentication.

4.29 Patch

429patches16478

 

Latest

Fixed an issue with Snowflake - Bulk Load Snap where Snap failed with 301 status code - SnapDataException.

4.29 Patch

429patches16458

 

Latest

  • Fixed the following issues with the Snaps that use Snowflake Accounts Key Pair Authentication.

    • The Snaps were not able to read the private keys provided as Pipeline parameters, because the key was malformed by replacing the line breaks with whitespace characters. Now, the private keys are properly formed and read when provided as Pipeline parameters.

    • The Snap displayed a Null Point Exception error when you pass an invalid key into the Private Key field like test. Now, the Snap displays a valid error message.

  • Fixed an issue with the Snaps due to an upgrade made to HikariCP that caused a conditional failure and prevented the downstream Snaps to supply the parameters to the stored procedure.  

  • Fixed an issue with Snowflake Execute and Snowflake Select Snaps where the Snap displayed an exception error when the FLOAT or DOUBLE datatype column has the value as NaN (Not a Number). Now the output value is written as-is (NaN) for FLOAT or DOUBLE datatype column and does not display an exception.

  • Enhanced the following Snowflake Accounts with support for Key Pair Authentication.

  • Removed support for unencrypted Private Keys to enforce security in Snowflake accounts.

4.29

main15993

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.28 Patch

428patches15236

 

Latest

  • Updated the Snowflake - Bulk Upsert Snap for the following:

    • The Snap displayed a incorrect resolution when the length of the value exceeded the value defined in a column.

    • The Snap failed with a NullPointer Exception when no value was provided for Error Limit field and Error percentage limit fields.

    • The Snap displayed an incorrect error message when S3 details were not provided.

    • Added the On Error dropdown list, where you can select an action to perform when the Snap encounters errors in a file.

  • Removed the Username field in the following accounts to allow reusing of accounts among different users:

  • The following enhancements were done for Snowflake - Bulk Load Snap:

    • The Snap skips AWS account validation if S3 Storage Integration property is provided.

    • The Snap skips the validate command if S3 Storage Integration property is not provided

    • The Snap overrides the storage integration specified in the account settings with the storage integration specified in the Snap settings.

  • Enhanced the Snowflake - Unload Snap to skip AWS account validation if S3 Storage Integration property is provided.

4.28

main14627

 

Stable

4.27

427patches12999

 

Latest

Enhanced the Snowflake SCD2 Snap to support Pipeline parameters for Natural key and Cause-historization fields.

4.27

main12833

 

Stable

  • Enhanced the Snowflake S3 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.

  • Added the following truncate options to Snowflake - Bulk Load Snap to truncate existing data before performing data load to more efficiently transfer data where possible.

    • Truncate data: Truncates existing data before performing data load. 

    • Truncate columns: Truncates column values that are larger than the maximum column length in the table.

  • Enhanced the Snowflake - Execute Snap to invoke stored procedures.

4.26 Patch

426patches11469

 

Latest

Fixed an issue with Snowflake Insert and Snowflake Bulk Load Snaps where the schema names or database names containing underscore (_) caused the time out of Pipelines.

4.26

main11181

 

Stable

  • Enhanced Snowflake - Lookup and Snowflake SCD2 Snaps with the Input Date Format field to select from the following two options:

    • Continue to execute the snap with the given input Date format

    • Auto Convert the format to Snowflake default format

  • Added a new account type Snowflake Google Storage Database to connect to Google Cloud Storage to load data.

  • Added support for all existing Snowflake Snap accounts to connect to a Snowflake instance hosted on the Google Cloud Platform

4.25

425patches10190

Latest

Enhanced the Snowflake S3 Database and Snowflake S3 Dynamic accounts with a new field S3 AWS Token that allows you to connect to private and protected Amazon S3 buckets.

4.25

main9554

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.24 Patch

424patches8905

 

Latest

Enhanced the Snowflake - Bulk Load Snap to allow transforming data using a new field Select Query before loading data into the Snowflake database. This option enables you to query the staged data files by either reordering the columns or loading a subset of table data from a staged file. This Snap supports CSV and JSON file formats for this data transformation.

4.24

main8556

Stable

Enhanced the Snowflake - Select Snap to return only the selected output fields or columns in the output schema (second output view) using the Fetch Output Fields In Schema check box. If the Output Fields field is empty all the columns are visible.

4.23 Patch

423patches7905

 

Latest

Fixed the performance issue in the Snowflake - Bulk Load Snap while using External Staging on Amazon S3.

4.23

main7430

 

Stable

4.22 Patch 

422patches7246

 

Latest

Fixed an issue with the Snowflake Snaps that failed while displaying similar error in the Snowflake URL connection: message, javax.management.MalformedObjectNameException: Invalid character '=' in value part of property, repeatedly when there is "=" or ":" .

4.22 Patch

422patches6849

 

Latest

4.22

main6403

 

Stable

Updated 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

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

  • Fixed the exception RefCnt has gone negative across the Snaps in the Snowflake Snap Pack.

4.21 Patch 

db/snowflake8860

 

Latest

Added a new field, Handle Timestamp and Date Time Data, to Snowflake Lookup Snap. This field enables you to decide whether the Snap should translate UTC time to your local time and the format of the Date Time data.

4.21 Patch

MULTIPLE8841

 

Latest

Fixed 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 

db/snowflake8800

 

Latest

  • Certifies the Snowflake Snap Pack against JDBC Driver version 3.12.3. Snowflake Execute and Multi-Execute Snaps may break existing Pipelines if the JDBC Driver is updated to a newer version.

  • With the updated JDBC driver (version 3.12.3), the Snowflake Execute and Multi-Execute Snaps' output displays a Status of "-1" instead of "0" without the Message field upon successfully executing DDL statements. If your Pipelines use these Snaps and downstream Snaps use the Status field's value from these, you must modify the downstream Snaps to proceed on a status value of -1 instead of 0.

  • This change in the Snap behavior follows from the change introduced in the Snowflake JDBC driver in version 3.8.1:
    "Statement.getUpdateCount() and PreparedStatement.getUpdateCount() return the number of rows updated by DML statements. For all other types of statements, including queries, they return -1."

4.20 Patch 

db/snowflake8758

 

Latest

Re-release of fixes from db/snowflake8687 for 4.20: Fixes the Snowflake Bulk Load snap where the Snap fails to load documents containing single quotes when the Load empty strings checkbox is not selected.

4.20

snapsmrc535

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.19 Patch 

db/snowflake8687

 

Latest

Fixed the Snowflake Bulk Load snap where the Snap fails to load documents containing single quotes when the Load empty strings checkbox is not selected.

4.19 Patch 

db/snowflake8499

 

Latest

Added the property Handle Timestamp and Date Time Data to Snowflake - Execute and Snowflake - Select Snaps. This property enables you to decide whether the Snap should translate UTC time to your local time.

4.19 Patch 

db/snowflake8412

 

Latest

Fixed an issue with the Snowflake - 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

  • Added a new field-set, Auto Historization Query, in the Snowflake SCD2 Snap to support auto-historization of column data. With this enhancement you can detect whether the incoming record is a historical event or a current event.  

  • Raised the minimum buffer size in the Snowflake - Bulk Upsert and Snowflake - Bulk Load Snaps to 6 MB.

4.18 Patch 

db/snowflake8044

 

Latest

Fixed an issue with the Snowflake - Select Snap wherein the Snap converts the Snowflake-provided timestamp value to the local timezone of the account.

4.18 Patch 

db/snowflake8044

 

Latest

Enhanced the Snap Pack to support AWS SDK 1.11.634 to fix the NullPointerException issue in the AWS SDK. This issue occurred in AWS-related Snaps that had HTTP or HTTPS proxy configured without a username and/or password. 

4.18 Patch

MULTIPLE7884

 

Latest

Fixed an issue with the PostgreSQL grammar to better handle the single quote characters.

4.18 Patch 

db/snowflake7821

 

Latest

Fixed an issue with the Snowflake - Execute Snap wherein the Snap is unable to support the '$' character in query syntax.

4.18 Patch

MULTIPLE7778

 

Latest

Updated the AWS SDK library version to default to Signature Version 4 Signing process for API requests across all regions.

4.18 Patch 

db/snowflake7739

 

Latest

  • Fixed an issue with the Snowflake - Bulk Upsert Snap wherein the Snap fails when using a pipeline parameter in Key columns.

  • Fixed an issue with the Snowflake - Unload Snap wherein the Snap does not abort the query when you stop the Pipeline execution.

4.18

snapsmrc523

 

Stable

Added the Use Result Query property to the Multi Execute Snap, which enables you to write results to an output view.

4.17

ALL7402

 

Latest

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

4.17 Patch 

db/snowflake7396

 

Latest

Fixed an issue wherein bit data types in the Snowflake - Select table convert to true or false instead of 0 or 1.

4.17 Patch 

db/snowflake7334

 

Latest

Added AWS Server-Side Encryption support for AWS S3 and AWS KMS (Key Management Service) for Snowflake Bulk Load, Snowflake Bulk Upsert, and Snowflake Unload Snaps.

4.17

snapsmrc515

 

Latest

  • Fixed an issue with the Snowflake 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 

db/snowflake6945

 

Latest

Fixed an issue with the Snowflake Lookup Snap failing when Date datatype is used in JavaScript functions.

4.16 Patch 

db/snowflake6928

 

Latest

Added support for file format options for input data from upstream Snaps, to the Snowflake Bulk Load Snap.

4.16 Patch 

db/snowflake6819

 

Latest

  • Snowflake Bulk Load: Added new property, Buffer size (MB). Configure this to specify the size limit of each buffer when writing to external staging systems such as S3. 

  • Fixed an issue with the Lookup Snap passing data simultaneously to output and error views when some values contained spaces at the end.

4.16

snapsmrc508

 

Stable

  • Snowflake Account: Added the ability to use SnapLogic to securely connect to and query a Snowflake instance using Azure Blob as its storage layer. 

  • Snowflake Account: Added support for Snowflake JDBC driver JAR version 3.6.17. 

  • Snowflake Unload, Bulk Load, and Bulk Upsert: Updated the Snaps to enable SnapLogic users to successfully connect to a Snowflake instance to query, bulk load, and unload data from Azure Blob storage.

4.15

snapsmrc500

 

Stable

  • Added two new Snaps, Snowflake - Multi Execute, and Snowflake SCD2. Snowflake - Multi Execute is used for executing multiple DDL and DML queries on the Snowflake DB. Snowflake SCD2 is used for Type 2 field historization. 

  • Enhanced the Snowflake Bulk Upsert Snaps to improve the Snaps performance.

  • Enhanced the Snowflake Snap Pack to reflect Azure certification.

4.14

snapsmrc490

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.13

snapsmrc486

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.12

snapsmrc480

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.11 Patch

MULTIPLE4377

 

Latest

Fixed a document call issue that was slowing down the Snowflake Bulk Load Snap.

4.11 Patch 

db/snowflake4283

 

Latest

Snowflake Bulk Load - Fixed an issue by adding PUT command to the list of DDL command list for Snowflake.

4.11 Patch 

db/snowflake4273

 

Latest

Snowflake Bulk Load - Resolved an issue with Snowflake Bulk Load Delimiter Consistency (comma and newline).

4.11

snapsmrc465

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.10 Patch

snowflake4133

Latest

Updated the Snowflake Bulk Load Snap with Preserve case sensitivity property to preserve the case sensitivity of column names.

4.10

snapsmrc414

 

Stable

  • Updated the Snowflake Bulk Load Snap with Load empty strings property for the empty string values in the input documents to be loaded as empty strings to the string-type fields.

  • Updated the Snowflake Bulk Load Snap with Table Columns to support the order of the entries on the staged files that contain a subset of the columns in the Snowflake table.

  • Added the property Use Result Query to view the output preview field with a result statement.

  • Tested for the JDBC driver JAR version 3.1.1 on the Database and the Dynamic accounts.

4.9.0 Patch

snowflake3234

 

Latest

Enhanced Snowflake - Execute Snap results to include additional details

4.9.0 Patch

snowflake3125

 

Latest

Addressed an issue in Snowflake Bulk Load where the comma character in a value is not escaped.

4.9

snapsmrc405

 

Stable

JDBC Driver Class property added to enable the user to custom configure the JDBC driver in the Database and the Dynamic accounts.

4.8.0 Patch

snowflake2760

 

Latest

Potential fix for JDBC deadlock issue.

4.8.0 Patch

snowflake2739

 

Latest

Addressed an issue with the Snowflake schema not correctly represented in the Mapper Snap.

4.8

snapsmrc398

 

Stable

  • Info tab added to accounts.

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

  • Enhanced the default count of input and output view (UI) behavior of the Snaps for better user experience. Note that the Snowflake Select, Table List and Lookup Snap views remain unchanged.

  • No labels