Configuring the ArgoDB output widget lets you write data from an external database into ArgoDB, or to transfer and synchronize data from a connected storage system to ArgoDB for data integration and reprocessing. This topic explains the configuration process for the ArgoDB output widget.
Limits
The ArgoDB output widget supports writing to ArgoDB data tables in file formats such as orc, parquet, text, and holedesk. However, it does not support integration with transactional tables in ORC format.
Prerequisites
Before beginning the operation, ensure you have completed the following:
Creation of an ArgoDB data source. For more information, see Create an ArgoDB data source.
To configure ArgoDB output properties, the account must have read-through permission for the data source. If you lack the necessary permissions, you need to request access to the data source. For more information, see Request data source permission.
Procedure
On the Dataphin home page, select Development > Data Integration from the top menu bar.
On the integration page's top menu bar, select Project (Dev-Prod mode requires selecting an environment).
In the navigation pane on the left, click Offline Integration. In the Offline Integration list, click the desired Offline Pipeline to open its configuration page.
Click Component Library in the upper right corner of the page to open the Component Library panel.
In the Component Library panel's left-side navigation pane, select Output. Find the ArgoDB widget in the output widget list on the right and drag it onto the canvas.
Click and drag the
icon from the target upstream widget to connect it to the ArgoDB output widget.Click the
icon on the ArgoDB output component card to open the ArgoDB Output Configuration dialog box.
In the ArgoDB Output Configuration dialog box, set the parameters as outlined in the table below.
Parameter
Description
Basic Settings
Step Name
This is the name of the ArgoDB output widget. Dataphin automatically generates the step name, but you can modify it based on your business scenario. The naming convention is as follows:
Can only contain Chinese characters, letters, underscores (_), and numbers.
Cannot exceed 64 characters.
Datasource
The data source dropdown list displays all ArgoDB-type data sources, including those for which you have write-through permission and those for which you do not. Click the
icon to copy the current data source name.For data sources without write-through permission, you can click Request after the data source to request write-through permission. For more information, see Request, Renew, and Return Data Source Permissions.
If you do not yet have an ArgoDB-type data source, click Create Data Source to create a data source. For more information, see Create an ArgoDB Data Source.
Table
Select the data table to be integrated according to the actual scenario requirements. Click the
icon to copy the name of the currently selected table.ImportantIf the table schema changes, you need to reconfigure the pipeline task.
File Encoding
Select the encoding format based on the actual data situation. Supports UTF-8 and GBK.
Loading Policy
Overwrite Data: This means that the current source table is used as the standard to overwrite historical data in the target table. Under the overwrite data policy, when there is a primary key/constraint violation, the original data will be deleted first, and then the entire new row of data will be inserted.
Append Data: This means that data is appended to the existing data in the target table without modifying historical data. Under the append data policy, when there is a primary key/constraint violation, a dirty data fault will be prompted. The append data policy does not support merging.
Compression Format
This is an optional field. If the file is compressed, select the corresponding compression format to facilitate decompression by Dataphin.
Field Separator
The string separator set is used to write to the target data source. If not filled in, the default is \u0001.
Preparation Statement
The SQL script executed on the database before data import, within 128 characters.
End Statement
The SQL script executed on the database after data import, within 128 characters.
Field Mapping
Input Field
The input fields are displayed for you based on the output of the upstream widget.
Output Field
The output field area displays all fields of the selected table. If certain fields do not need to be output to the downstream widget, you can delete the corresponding fields:
To delete a small number of fields, you can click the Actions column's
icon to delete the extra fields.To delete many fields, you can click Field Management, select multiple fields on the Field Management page, and then click the
icon to move the Selected Input Fields to Unselected Input Fields. 
Mapping
The mapping relationship is used to map the input fields of the source table to the output fields of the target table. The mapping relationship includes same-name mapping and same-row mapping. The applicable scenarios are described as follows:
Same-name Mapping: Maps fields with the same field name.
Same-row Mapping: The field names of the source table and target table are inconsistent, but the data in the corresponding rows of the fields needs to be mapped. Only fields in the same row are mapped.
Click Confirm to finalize the ArgoDB output widget configuration.