Dataphin:Configure Teradata input component

Limits

Reading views from Teradata databases is not supported.

Prerequisites

• A Teradata data source is created. For more information, see Create a Tablestore data source.

• The account used to configure the Teradata input component must have the read-through permission on the data source. If you do not have the permission, request it. For more information, see Request data source permissions.

Procedure

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

2. In the top navigation bar of the Integration page, select a project (In Dev-Prod mode, you need to select an environment).

3. In the left-side navigation pane, 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 left-side navigation pane of the Component Library panel, select Inputs. Find the Teradata component in the input component list on the right and drag it to the canvas.

6. Click the icon in the Teradata input component card to open the Teradata Input Configuration dialog box.

7. In the Teradata Input Configuration dialog box, configure the parameters.

   Parameter	Description
   Step Name	The name of the Teradata input component. Dataphin automatically generates a step name, which you can modify as needed. 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 in the current Dataphin instance, including those you have the read-through permission for and those you do not. Click the icon to copy the current data source name. For data sources you do not have the read-through permission for, click Request next to the data source to request the read-through permission. For more information, see Request data source permissions. If no Teradata data source exists, click Create Data Source to create one. For more information, see Create a Tablestore data source.
   Table	Enter a table name keyword to search for tables, or enter an 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 selected table name.
   Shard Key (optional)	The system shards data based on the configured shard key field. Use this parameter with concurrent reading to enable parallel reads. You can use a column in the source table as the shard key. We recommend that you use the primary key or an indexed column to ensure transmission performance. Important When you select a date and time type, the system identifies the maximum and minimum values, and performs forced sharding based on the total time range and concurrency. Even distribution is not guaranteed.
   Batch Read Count (optional)	The number of data records to read at a time. Configure a batch read count (such as 1,024 records) instead of reading records one by one. This reduces interactions with the data source, improves I/O efficiency, and lowers network latency.
   Input Filter (optional)	The filter condition for extracting data. You can configure filters as follows: Configure a static field: Extract the corresponding data, for example, ds=20210101. Configure a variable parameter: Extract a specific part of the data, for example, ds=${bizdate}.
   Output Fields	Displays all fields that match the selected table and filter conditions. You can perform the following operations: Field Management: To exclude certain fields from downstream components, delete them: Delete a single field: Click the icon in the Operation column to delete a field. Delete multiple fields in batches: Click Field Management. In the Field Management dialog box, select the fields to remove, click the left arrow icon to move them to the unselected list, and then click OK. Batch Add: Click Batch Add to configure fields in JSON, TEXT, or DDL format in batches. Note After you complete the batch addition and click OK, the configured field information will be overwritten. Configure fields in JSON format in batches, for example: // Example: [{ "index": 1, "name": "id", "type": "int(10)", "mapType": "Long", "comment": "comment1" }, { "index": 2, "name": "user_name", "type": "varchar(255)", "mapType": "String", "comment": "comment2" }] Note index indicates the column number of the specified object, name indicates the field name after import, and type indicates the field type after import. For example, "index":3,"name":"user_id","type":"String" indicates that the fourth column in the file is imported, the field name is user_id, and the field type is String. Configure fields in TEXT format in batches, for example: // Example: 1,id,int(10),Long,comment1 2,user_name,varchar(255),Long,comment2 The row delimiter is used to separate the information of each field. The default is a line feed (\n). Line feeds (\n), semicolons (;), and periods (.) are supported. The column delimiter is used to separate the field name from the field type. The default is a comma (,). The supported delimiter is ','. The field type can be omitted. The default is ','. Configure fields in DDL format in batches, for example: CREATE TABLE tablename ( user_id serial, username VARCHAR(50), password VARCHAR(50), email VARCHAR (255), created_on TIMESTAMP, ); Create an output field: Click + Create Output Field, specify Column, Type, and Remarks, and select a Mapping Type. Click the icon to save the row.

8. Click OK to complete the property configuration of the Teradata Input Component.