tSnowflakeOutput Standard properties
These properties are used to configure tSnowflakeOutput running in the Standard Job framework.
The Standard tSnowflakeOutput component belongs to the Cloud family.
The component in this framework is available in all Talend products.
Basic settings
| Database |
Select the desired database type from the list and click Apply. |
|
Property Type |
Select the way the connection details will be set.
This property is not available when other connection component is selected from the Connection Component drop-down list. |
|
Connection Component |
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. |
| Authentication Type |
Set the authentication type.
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.
|
| OAuth token endpoint | Enter OAuth 2.0 token endpoint. This option is available when OAuth 2.0 is selected from the Authentication Type drop-down list. |
| Client ID | Enter the client ID of your application. This option is available when OAuth 2.0 is selected from the Authentication Type drop-down list. |
| Client Secret | Enter the client secret of your application. This option is available when OAuth 2.0 is selected from the Authentication Type drop-down list. |
| Grant type | Set the grant type for retrieving the access token. Two options are
provided: Client Credentials and
Password. Click Client Credentials and Resource Owner Password Credentials for related information. This option is available when OAuth 2.0 is selected from the Authentication Type drop-down list. |
| OAuth username | Enter the OAuth username. This option is available when Password is selected from the Grant type drop-down 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 drop-down list. Information noteNote: OAuth password does not support spaces.
|
| Scope | Enter the scope. See Scopes for related information. This option is available when OAuth 2.0 is selected from the Authentication Type drop-down list. |
| User Id and Password |
Enter, in double quotation marks, your authentication information to log in to Snowflake.
|
| 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. |
| 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. |
| 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. |
| Table |
Click the [...] button and in the displayed wizard, select the Snowflake table to be used. |
| 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:
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. 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.
|
| 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.
|
| Die on error |
Select this option to stop the execution of the Job when an error occurs; clear this option to skip any rows on error and complete the process for error-free rows. This option cannot work with Row > Reject connections. |
Advanced settings
| Additional JDBC Parameters |
Specify additional JDBC parameters for the database connection created. |
| 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. |
| Region ID (Deprecated) | Enter a region ID in double quotation marks, for example
eu-west-1 or east-us-2.azure. For
information about Snowflake Region ID, see Supported Cloud Regions. 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 check box 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 check box, all identifiers are automatically quoted. This property is not available when you select the Manual Query check box. For more information on the Snowflake Identifier Syntax, see Identifier Syntax. |
| Convert empty strings to null | Select this option to convert empty strings to null. |
| Use existing database schema as the dynamic schema | If you are using the dynamic schema feature, select this check box 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. |
| 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 drop-down list in the Basic settings view. |
| Custom DB Type | Select this check box 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 | Select this check box to use a custom mapping for your date type date, and
then select the mapping from the Convert Date values to
drop-down list. This option is available when you use a dynamic schema and when
you select the following option from the Table Action
drop-down list in the Basic settings view:
|
| 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. |
|
tStatCatcher Statistics |
Select this check box to gather the Job processing metadata at the Job level as well as at each component level. |
Global Variables
|
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 rule |
This component is end component of a data flow in your Job. It receives data fromRow > Main link. It can also send error messages to other components via a
Row > Rejects link. The provided
information about an error could be:
|