Configure Teradata output component

Prerequisites

• You have created a Teradata data source. For more information, see Create a Teradata data source.

• The account used to configure the Teradata output component properties has write-through permission for the data source. If you do not have this permission, you need to request it. For more information, see Request data source permissions.

Limits

Writing data to views in a Teradata database is not supported.

Procedure

1. In the top navigation bar of the Dataphin homepage, choose Develop > Data Integration.

2. In the top navigation bar of the integration page, select Project (In Dev-Prod mode, you need to select Environment).

3. In the navigation pane on the left, click Batch Pipeline. In the Batch Pipeline list, click the offline pipeline that you want to develop to open its configuration page.

4. Click Component Library in the upper-right corner of the page to open the Component Library panel.

5. In the navigation pane on the left of the Component Library panel, select Outputs. Find the Teradata component in the output component list on the right, and drag it to the canvas.

6. Click and drag the icon of the target input, transform, or flow component to connect it to the current Teradata output component.

7. Click the icon in the Teradata output component card to open the Teradata Output Configuration dialog box.

8. In the Teradata Output Configuration dialog box, configure the parameters.

   Parameter		Description
   Basic Settings	Step Name	The name of the Teradata output component. Dataphin automatically generates a step name that you can modify. The name must meet the following requirements: It can contain only Chinese characters, letters, underscores (_), and digits. It cannot exceed 64 characters in length.
   	Datasource	The dropdown list displays all Teradata data sources, regardless of whether you have write-through permission. Click the icon to copy the data source name. For data sources without write-through permission, click Request next to the data source to request permission. For more information, see Request data source permissions. If you do not have a Teradata data source, click Create Data Source to create one. For more information, see Create a Teradata data source.
   	Table	Select the target table for output data. You can enter a keyword to search for tables or enter the exact table name and click Exact Match. After you select a table, the system automatically checks the table status. Click the icon to copy the name of the selected table.
   	Loading Policy	Select the loading policy. Only the Append Data policy is supported. The overwrite policy is not supported. Under the Append Data policy, a dirty data error is reported when a primary key or constraint violation occurs.
   	Batch Write Size (optional)	The amount of data written per batch. You can also set Batch Write Records. The system writes data when either limit is reached. The default value is 32M.
   	Batch Write Records (optional)	The default value is 2048 records. During data synchronization, the batch write strategy uses both Batch Write Records and Batch Write Size. When the accumulated data reaches either limit, the system immediately writes the batch to the destination. We recommend that you set the batch write size to 32MB. Adjust the batch write records based on the actual record size, typically to a large value to maximize batch writing efficiency. For example, if a single record is about 1KB and you set the batch write size to 16MB, set the batch write records to a value greater than 16MB / 1KB = 16384, such as 20000 records. With this configuration, a write operation is triggered when the accumulated data reaches 16MB.
   	Prepare Statement (optional)	An SQL script to run on the database before data import. For example, to ensure continuous service availability, the step first creates a target table Target_A and writes data to it. After the write completes, it renames the active Service_B table to Temp_C, renames Target_A to Service_B, and then deletes Temp_C.
   	Post Statement (optional)	An SQL script to run on the database after data import.
   Field Mapping	Input Fields	Displays input fields based on the output of the upstream component.
   	Output Fields	Displays the output fields. You can perform the following operations: Field Management: Click Field Management to select output fields. Click the icon to move Selected Output Fields to Unselected Output Fields. Click the icon to move Unselected Output Fields to Selected Output Fields. Batch Add: Click Batch Add to configure in JSON, TEXT, or DDL format. Batch configuration in JSON format, for example: // Example: [{ "name": "user_id", "type": "String" }, { "name": "user_name", "type": "String" }] Note The `name` parameter specifies the field name, and the `type` parameter specifies the data type after import. For example, "name":"user_id","type":"String" imports the field `user_id` with data type String. Batch configuration in TEXT format, for example: // Example: user_id,String user_name,String The row delimiter is used to separate the information of each field. The default is a line feed (\n). Line feed (\n), semicolon (;), and period (.) are supported. The column delimiter is used to separate the field name and field type. The default is a comma (,). Batch configuration in DDL format, for example: CREATE TABLE tablename ( id INT PRIMARY KEY, name VARCHAR(50), age INT ); Create Output Field: Click +Create Output Field, fill in the Column and select the Type as prompted. After completing the configuration for the current row, click the icon to save.
   	Mapping	Map upstream input fields to target table fields. Mapping includes Same Row Mapping and Same Name Mapping. Same Name Mapping: Maps fields with the same name. Same Row Mapping: Maps fields in the same row when the source and target field names differ but the row data needs to be mapped.

9. Click OK to complete the property configuration of the Teradata output component.