# tSnowflakeOutputBulkExec Writes incoming data to files generated in a folder and then loads the data into a Snowflake database table. The folder can be in an internal Snowflake stage, an Amazon Simple Storage Service (Amazon S3) bucket, or an Azure container. This component incorporates the operations of the tSnowflakeOutputBulk and the tSnowflakeBulkExec components. Information noteNote: This component is not shipped with your Talend Studio by default. You need to install it using the Feature Manager. For more information, see [Installing features using the Feature Manager](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/install-features-to-talend-studio). ## tSnowflakeOutputBulkExec Standard properties These properties are used to configure tSnowflakeOutputBulkExec running in the Standard Job framework. The Standard tSnowflakeOutputBulkExec component belongs to the Cloud family. The component in this framework is available in all subscription-based Talend products. Information noteNote: This component is a specific version of a dynamic database connector. The properties related to database settings vary depending on your database type selection. For more information about dynamic database connectors, see [DB Generic components](https://help.qlik.com/talend/r/en-US/8.0/components/db-generic/db-generic-component). ## Basic settings | Properties | Description | | --- | --- | | Database | Select the desired database type from the list and click
Apply. | | Property Type | Select the way the connection details will be
set.

Built-In: The connection details will be set locally for this component. You need to specify the values for all related connection properties manually.
Repository: The connection details stored centrally in Repository > Metadata will be reused by this component. You need to click the [...] button next to it and in the pop-up Repository Content dialog box, select the connection details to be reused, and all related connection properties will be automatically filled in.

This property is available when Use this Component is
selected from the Connection Component dropdown
list. | | Component list | Select the component that opens the database connection to be reused by this
component. | | Account | In the Account field, enter, in double
quotation marks, the account name that has been assigned to you by Snowflake.

This field is available only when Use this
Component is selected from the Connection
Component dropdown list. | | Authentication Type | Set the authentication type.

Basic: Select this option if key pair authentication is not enabled.
Key Pair: Select this option if key pair authentication is enabled.

See Using Key Pair Authentication for related information.
OAuth 2.0: Select this option to use external OAuth for data accessing.

See External OAuth Overview for related information.

Information noteNote: Before selecting the Key
Pair option, make sure you have set the key pair authentication
data in the Basic settings view of the tSetKeystore
component as follows.

Leave the TrustStore type field unchanged.
Set TrustStore file to "".
Clear the TrustStore password field.
Select Need Client authentication.
Enter the path to the key store file in double quotation marks in the KeyStore file field (or click the […] button to the right of the KeyStore file field and navigate to the key store file).
Enter the key store file password in the KeyStore password field.
Clear the Check server identity option.

| | OAuth token endpoint | Enter OAuth 2.0 token endpoint.

This option is available when
OAuth 2.0 is selected from the
Authentication Type dropdown list. | | Client ID | Enter the client ID of your application.

This option is available when
OAuth 2.0 is selected from the
Authentication Type dropdown list. | | Client Secret | Enter the client secret of your application.

This option is available when
OAuth 2.0 is selected from the
Authentication Type dropdown list. | | Grant type | Set the grant type for retrieving the access token. Two options are
provided: Client Credentials and
Password.

Click [Client Credentials](https://tools.ietf.org/html/rfc6749#section-1.3.4) and [Resource Owner Password Credentials](https://tools.ietf.org/html/rfc6749#section-1.3.3) for related
information.

This option is available when OAuth
2.0 is selected from the Authentication
Type dropdown list. | | OAuth username | Enter the OAuth username.

This option is available when
Password is selected from the Grant
type dropdown list. | | OAuth password | Enter the OAuth password.

To enter the password, click the [...] button
next to the password field, enter the password between double quotes in the
pop-up dialog box, and then click OK to save the
settings.

This option is available when Password
is selected from the Grant type dropdown
list.

Information noteNote: OAuth password does not support spaces. | | Scope | Enter the scope. See [Scopes](https://docs.snowflake.com/en/user-guide/oauth-ext-overview.html#scopes) for related information.

This option is
available when OAuth 2.0 is selected from the
Authentication Type dropdown list. | | User Id and Password | Enter, in double quotation marks, your authentication information to
log in to Snowflake.

In the User ID field, enter, in double quotation marks, your login name that has been defined in Snowflake using the LOGIN_NAME parameter of Snowflake. For details, ask the administrator of your Snowflake system.
To enter the password, click the [...] button next to the password field, enter the password in double quotes in the pop-up dialog box, and click OK to save the settings.

This field is available only when Use this
Component is selected from the Connection
Component dropdown list. | | Warehouse | Enter, in double quotation marks, the name of the
Snowflake warehouse to be used. This name is case-sensitive and is normally upper
case in Snowflake.

This field is available only when Use this
Component is selected from the Connection
Component dropdown list. | | Schema | Enter,
within double quotation marks, the name of the database schema to be used. This name
is case-sensitive and is normally upper case in Snowflake.

This field is available only when Use this
Component is selected from the Connection
Component dropdown list. | | Database | Enter, in double quotation
marks, the name of the Snowflake database to be used. This name is case-sensitive
and is normally upper case in Snowflake.

This field is available only when Use this
Component is selected from the Connection
Component dropdown list. | | Table | Click the [...] button and in the displayed wizard, select the
Snowflake table to be used.

To load the data into a new
table, select Use custom object in the
wizard and enter the name of the new table in Object
Name field. | | Schema and Edit Schema | A schema is a row description. It defines the number of fields
(columns) to be processed and passed on to the next component. When you create a Spark
Job, avoid the reserved word line when naming the
fields.

Built-In: You create and store the schema locally for this component
only.

Repository: You have already created the schema and stored it in the
Repository. You can reuse it in various projects and Job designs.

If the Snowflake data type to be handled is VARIANT, OBJECT, or ARRAY, while
defining the schema in the component, select String for the
corresponding data in the Type column of the schema editor
wizard.

Click Edit
schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

View schema: choose this option to view the schema only.
Change to built-in property: choose this option to change the schema to Built-in for local changes.
Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

Note that if the input value of any non-nullable
primitive field is null, the row of data including that field will be
rejected.

This component offers the advantage of the
dynamic schema feature. This allows you to retrieve unknown columns from source
files or to copy batches of columns from a source without mapping each column
individually. For further information about dynamic schemas, see [Dynamic schema](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/dynamic-schema).

This
dynamic schema feature is designed for the purpose of retrieving unknown columns of a
table and is recommended to be used for this purpose only; it is not recommended for the
use of creating tables. | | Table Action | Select the action to be carried out to the table.

NONE: Leave the table as is.
DROP_CREATE: Remove the table and create it again.
CREATE: Create a new table.
CREATE_IF_NOT_EXISTS: Create the table if it does not exist.
DROP_IF_EXISTS_AND_CREATE: Remove the table if it already exists and create again.
CLEAR: Remove all the data records in the table.
TRUNCATE: Remove all the rows in the table. This action releases the space occupied by the table.

| | Output Action | Select the operation you want to perform to the incoming data and data
records in the Snowflake database table. You can insert, delete, update, or merge
data in the Snowflake table. This option assumes that the Snowflake table
specified in Table field already exists.

INSERT: Insert new records in the Snowflake table.
Information noteNote: Because this operation uses the Snowflake COPY INTO command, which drops the use of temporary tables and currently does not support data validation, unexpected results may occur when you retrieve rejected records. See Transforming Data During a Load for related information.
UPDATE: Update existing records in the Snowflake table.
UPSERT: Create new records and update existing records. You need to specify a schema column as the join key from the Upsert Key Column dropdown list or specify to use the schema keys for the operation by selecting Use schema keys for upsert in the Advanced settings view.
Information noteNote: The Upsert Key Column dropdown list is available when Use schema keys for upsert is not selected.
DELETE: Remove records from the Snowflake table.

| | Storage | Select the type of storage to upload the incoming data to and to load data
into the table from.

Internal: Store the incoming data in a folder in the internal Snowflake storage and then load data from the folder. You need also to specify the folder within double quotation marks in Stage Folder.
S3: Store the incoming data in an Amazon S3 folder and then load data from the folder. You need also to provide information about your S3 user account, including Region, Access Key (within double quotation marks), Secret Key, Bucket (within double quotation marks), and Folder (within double quotation marks).
Azure: Store the incoming data in an Azure folder and then load data from the folder. You need also to provide information about your Azure user account, including Protocol, Account Name (within double quotation marks), Container (within double quotation marks), Folder (within double quotation marks), and SAS Token.

| | Stage Folder | Specify the folder under the Snowflake stage to write incoming data to and
to load data from.

This field is available when you select
Internal from the Storage dropdown list
in the Basic settings view. | | Region | Specify the region where the S3 bucket locates.

This field is available when you select
S3 from the Storage dropdown list in
the Basic settings view. | | Access Key and Secret Key | Enter the authentication information required to connect to the Amazon S3
bucket to be used.

To enter the password, click the [...]
button next to the password field, and then in the pop-up dialog box enter the
password between double quotes and click OK to save the
settings.

This field is available when you select
S3 from the Storage dropdown list in
the Basic settings view. | | Bucket | Enter the name of the bucket (in double quotation marks) to be used for
storing the incoming data and loading data from. This bucket must already exist.

This field is available when you select
S3 from the Storage dropdown list in
the Basic settings view. | | Folder | Enter the name of the folder (in double quotation marks) to be used for
storing the incoming data and loading data from. This folder will be created if it
does not exist at runtime.

This property is available only when
S3 or Azure is selected from
the Storage drop-down list. | | Server-Side Encryption | Select this checkbox to encrypt the files to be uploaded to the S3 bucket on
the server side. This property is checked by default.

This field is available when you select
S3 from the Storage dropdown list in
the Basic settings view. | | Protocol | Select the protocol used to create Azure connection.

This field is available when you select
Azure from the Storage dropdown list in
the Basic settings view. | | Account Name | Enter the Azure storage account name (in double quotation marks).

This field is available when you select
Azure from the Storage dropdown list in
the Basic settings view. | | Container and Folder | Enter the Azure container and folder names (in double quotation marks).

This field is available when you select
Azure from the Storage dropdown list in
the Basic settings view. | | SAS Token | Specify the SAS token to grant limited access to objects in your storage
account.

To enter the SAS token, click the [...]
button next to the SAS token field, and then in the pop-up dialog box enter the
password between double quotes and click OK to save the
settings.

This field is available when you select
Azure from the Storage dropdown list in
the Basic settings view. | ## Advanced settings | Properties | Description | | --- | --- | | Additional JDBC Parameters | Specify additional connection properties for the database connection you are
creating. The properties are separated by semicolon and each property is a key-value
pair, for example, *encryption=1;clientname=Talend*.

This field is available only when you select Use
this Component from the Connection Component
dropdown list and select Internal from the
Storage dropdown list in the Basic
settings view. | | Login Timeout | Specify the timeout period (in minutes)
of Snowflake login attempts. An error will be generated if no response is received
in this period. | | Role | Enter, in
double quotation marks, the default access control role to use to initiate the
Snowflake session.

This role must already exist and
has been granted to the user ID you are using to connect to Snowflake. If this field
is left empty, the PUBLIC role is automatically granted. For information about
Snowflake access control model, see [Understanding the Access Control
Model](https://docs.snowflake.net/manuals/user-guide/security-access-control.html). | | URL suffix | Enter, in double quotation marks, the Snowflake custom domain URL of your
choice. For more information about Snowflake URL formats, see [Standard account URLs](https://docs.snowflake.com/en/user-guide/organizations-connect#standard-account-urls).

For Snowflake components other than tSnowflakeConnection, this field is
available when you select Use This Component from the
Connection Component drop-down list in the
Basic settings view. | | Allow Snowflake to convert columns and tables to uppercase | Select this checkbox to convert lowercase in the defined table name and
schema column names to uppercase. Note that unquoted identifiers should match the
Snowflake Identifier Syntax.

If you deselect the checkbox, all identifiers are
automatically quoted.

This property is not available when you select the
Manual Query checkbox.

For more information on
the Snowflake Identifier Syntax, see [Identifier Syntax](https://docs.snowflake.net/manuals/sql-reference/identifiers-syntax.html). | | Use schema keys for upsert | Select this option to use schema keys for the Upsert operation. This option
is available when you select UPSERT from the Output
Action dropdown list in the Basic settings
view. | | Use existing database schema as the dynamic schema | If you are using the dynamic schema feature, select this checkbox to pick
the schema from the database itself (if the table exists). If this option is not
selected, the input schema is used by default. | | Temporary Table Schema | Specify a schema for the temporary table.

The schema must
exist. | | Use strict schema matching | Select this option to load incoming data to table columns whose column names
are exactly the same as those of the incoming data.

Column names are case
sensitive. If this option is not selected, it is possible that incoming data
are not loaded into the corresponding table columns.

This option is
available when INSERT is selected from the
Output Action drop-down list in the Basic
settings view.

Information noteNote: This option is available only when you
have installed the 8.0.1-R2023-04 Talend Studio Monthly update or a later one delivered by Talend. For more information, check with your administrator. | | Custom DB Type | Select this checkbox to specify the DB type for each column in the
schema.

This property is available only when you select an action with Create
Table from the Table Action drop-down list in the
Basic settings. | | Custom Date type mapping for creating table with dynamic
schema | If you are using the dynamic schema feature, select this checkbox to use a
custom mapping for your date type date, and then select the mapping from the
Convert Date values to dropdown list.

This option is
available when you select the following option from the Table
Action dropdown list in the Basic
settings view:

CREATE
DROP_CREATE
CREATE_IF_NOT_EXISTS

| | Use schema date pattern | Select this option to convert data
in schema columns that are of Date
type using the date pattern defined in the schema. To achieve this, you
need also to specify the DB type of the schema columns as STRING, TEXT, or VARCHAR in the
Custom DB Type
field. | | Delete Storage Files On Success | Delete all the files in the storage folder once the data is loaded to the
table successfully.

This field is not available when you select Use
Custom Storage Location. | | Use Custom Stage Path | Select this checkbox to upload the data to the files generated in a folder
under the stage. You need also to enter the path to the folder in the field
provided. For example, to upload data to the files generated in
myfolder1/myfolder2 under the stage, you need to type
"@~/myfolder1/myfolder2" in the field.

This field is available when you select
Internal from the Storage dropdown list
in the Basic settings view.

Once selected, the Stage Folder in Basic
settings view becomes unavailable. | | Use Custom S3 Connection Configuration | Select this checkbox if you wish to use your custom S3 configuration.

Option: select the parameter from the list.
Value: enter the parameter value.

This field is available when you select
S3 from the Storage dropdown list in
the Basic settings view. | | Copy Command Options | Set parameters for the COPY INTO command by selecting the following options
from the dropdown list. The COPY INTO command is provided by Snowflake. It loads
data to a Snowflake database table.

Default: Carry out the COPY INTO operation using the default settings, as listed in the frame to the right. When using Default, no read-only command text is generated.
Table: Set the COPY INTO operation parameters using the Options table. To set a parameter, click the plus button, select the parameter from the Option column, and set the parameter value in the Value column.
Manual: Set the COPY INTO operation parameters in the text frame to the right manually.

For information about the parameters of the COPY INTO command, see [the COPY INTO command](https://docs.snowflake.net/manuals/sql-reference/sql/copy-into-table.html). | | Put Command Options | Set parameters for the PUT command by selecting the following options from
the dropdown list. The PUT command is provided by Snowflake. It uploads data to a
Snowflake stage folder.

Default: Carry out the PUT operation using the default settings, as listed in the frame to the right. When using Default, no read-only command text is generated.
Table: Set the PUT operation parameters using the Options table. To set a parameter, click the plus button, select the parameter from the Option column, and set the parameter value in the Value column.
Manual: Set the PUT operation parameters in the text frame to the right manually.

For information about the parameters of the PUT command, see [the PUT command](https://docs.snowflake.net/manuals/sql-reference/sql/put.html).

This field is available when you select
Internal from the Storage dropdown list
in the Basic settings view. | | Put Command Error Retry | Specify the maximum data loading retries when an error occurs during loading
data to the internal Snowflake storage. This parameter defaults to 3. A value of
-1 specifies the maximum possible retries. Only
-1 or positive integers are accepted.

This field is available when you select
Internal from the Storage dropdown list
in the Basic settings view. | | Snowflake access to storage | Specifies the authentication method for the COPY command when accessing the S3
bucket. See [Additional Cloud Provider Parameters](https://docs.snowflake.com/en/sql-reference/sql/copy-into-table.html#additional-cloud-provider-parameters) for related information.

Information noteNote: This option is available when S3 is selected from the Storage drop-down list in the Basic settings view.

Credentials, uses the S3 credentials for the authentication.
Storage integration, uses a storage integration for the authentication. In this case, enter the integration name in the Storage integration field.

| | S3 assume role | If you temporarily need some access permissions associated to an AWS IAM
role that is not granted to your user account, select this checkbox to assume that
role. Then specify the values for the following parameters to create a new assumed
role session.

Ensure that access to this
role has been granted to your user account by the trust policy associated to
this role. If you are not certain about this, ask the owner of this role or
your AWS administrator.

Information noteNote:

This option is available when S3 is selected from the Storage drop-down list in the Basic settings view.
Assumed role temporary credentials are requested from AWS STS in us-east-1 region.

Role ARN: the Amazon Resource Name (ARN) of the role to assume. You can find this ARN name on the Summary page of the role to be used on your AWS portal, for example, this role ARN could read like am:aws:iam::[aws_account_number]:role/[role_name].
Role session name: enter the name you want to use to uniquely identify your assumed role session. This name can contain upper- and lower-case alphanumeric characters with no spaces. You can also include underscores or any of the following characters: =,.@-.
Session duration: the duration (in minutes) for which you want the assumed role session to be active. This duration cannot exceed the maximum duration which your AWS administrator has set. The duration defaults to 15 minutes.

For an example about an IAM role and its related policy types, see [Create and Manage AWS IAM Roles](https://aws.amazon.com/blogs/security/now-create-and-manage-aws-iam-roles-more-easily-with-the-updated-iam-console/) from the AWS
documentation. | | S3 Max Error Retry | Specify the maximum data loading retries when an error occurs during loading
data to or from the S3 folder. This parameter defaults to 3. A value of
-1 specifies the maximum possible retries. Only
-1 or positive integers are accepted.

This field is available when you select
S3 from the Storage dropdown list in
the Basic settings view. | | Azure Max Error Retry | Specify the maximum data loading retries when an error occurs during loading
data to or from the Azure folder. This parameter defaults to 3. A value of
-1 specifies the maximum possible retries. Only
-1 or positive integers are accepted.

This field is available when you select
Azure from the Storage dropdown list in
the Basic settings view. | | Non-empty Storage Folder Action | Select any of the following options:

Add New Files: continues to process the Job even if the selected storage folder already contains files and adds new files to the folder.
Cancel Upload: stops the operation when the storage folder used for loading data is not empty.
Replace Existing Files: cleans the storage folder before adding new files.

| | Chunk Size (bytes) | Specify the size for the files generated, which defaults to 52428800
bytes.

With this option specified, the incoming data may be stored in
multiple files. Since data is stored in files on a record base, the actual size
of each file generated can be larger or smaller than the specified value, but
no more than the size of the last record stored in the file.

Set this option
carefully as it can significantly affect the performance. See [File Sizing Best Practices and Limitations](https://docs.snowflake.net/manuals/user-guide/data-load-considerations-prepare.html#file-sizing-best-practices-and-limitations) for related
information. | | Number of file requests threads | Specify the number of threads used for sending Put
requests in parallel when writing the data in the files. | | tStatCatcher Statistics | Select this checkbox to gather the Job processing metadata at the Job level
as well as at each component level. | ## Global Variables | Variables | Description | | --- | --- | | NB\_LINE | The number of rows processed. This is an After variable and
it returns an integer. | | NB\_SUCCESS | The number of rows successfully processed. This is an After
variable and it returns an integer. | | NB\_REJECT | The number of rows rejected. This is an After variable and
it returns an integer. | | ERROR\_MESSAGE | The error message generated by the component when an error
occurs. This is an After variable and it returns a string. | ## Usage | Usage guidance | Description | | --- | --- | | **Usage rule** | This component is an end component
of a data flow in your Job. It receives data from other components
through the Row > Main link.

It can also send error messages to other components via a Row >
Rejects link. The provided information about an error could
be:

The name of the column in error.
The number of the row in error.
The category of the error, such as a parsing error or a conversion error.
The character offset in the line in error.
The related error message.
The offset of the byte in error.
The number of the line in error.
SQLSTATE for the error.
Snowflake error code.

| **Related concepts** * [Processing Parquet data using Snowflake components](https://help.qlik.com/talend/en-US/components/8.0/snowflake/processing-parquet-data-using-snowflake-components "This scenario shows the way to load data from a Parquet file into a Snowflake table and to retrieve the data from the Snowflake table.")