Create and manage tag offline services

Limitations

To ensure high availability of data, tag offline services write data into a temporary table ({target table}_dpfx_b). Once the data writing is complete, the original target table is renamed ({target table}_dpfx_tmp), and the temporary table is then renamed to the target table. Finally, the original target table ({target table}_dpfx_tmp) is deleted. Data is briefly unavailable from when the original target table is renamed until the temporary table is renamed to the target table.

Prerequisites

• Before creating a tag offline service, ensure you have selected the required tags in the tag asset market and obtained usage permissions for the application where the service will be located. For specific operations, see request tag permissions.

• The application associated with the tag offline service must already be created. For specific operations, see create and manage application.

• Before creating a tag offline service, you need to create the corresponding entity. For specific operations, see create and manage entity.

Create tag offline service

1. On the Dataphin home page, select Tag > Tag Application from the top menu bar.

2. In the left-side navigation pane, select Service Management > Tag Offline Service.

3. On the Tag Offline Service page, click Create Task.

4. On the Create Offline Service configuration page, set the required parameters.

   Parameter		Description
   Basic Information	Task Name	Enter the name of the offline task. Chinese, English, numbers, and underscores (_) are allowed, within 64 characters.
   	Application Selection	Select the application associated with the project.
   	Owner	Select the owner of the offline service. You can search by keyword.
   	Entity	Select the entity for the offline service.
   	Entity ID Selection	Select the entity ID. Note In Field Mapping, Enter Tag to filter the optional tag range based on the selected entity ID.
   	Schedule Type	Supports recurring schedule and manual schedule task types. Manual Schedule: One-time integration. After the task is published, you can select manual execution on the task list page. Recurring Schedule: Scheduled execution according to the configured recurring schedule.
   	Description	Enter a brief description, within 1000 characters.
   Field Mapping	Target Data Source	Select the target data source for the offline service. Supported types include MySQL, Oracle, AnalyticDB for PostgreSQL, Greenplum, openGauss, and Dataphin project. Note The target data source of the project only supports projects joined by the current account (General and Tag project), and the project tenant account has write-through permission. If no suitable data source exists, you can click +create Data Source to create one. For specific operations, see data source management.
   	Schema	For openGauss data sources, you can select the schema.
   	Target Table	Select the target table in the data source. For openGauss, select the target table under the schema. Multi-level partitioned tables are not supported. When cross-project safe mode is enabled, cross-project table creation is not supported. For more information, see security settings. If you do not have write table data permission for the current target table production environment, you can click Request Permission to apply for permission. For more information, see request, renew, and return table permissions. If there is no corresponding target table, after selecting Enter Tag, you can click One-click Create Table to create the required target table. In the system-generated create table statement, confirm whether the table name, field type, precision, etc., meet the requirements before clicking Create. The table name and table comments are automatically generated by the system and can be modified as needed. The system-generated create table statement refers to the type of input tag and performs preliminary transformation, which you can modify as needed. When the target data source is a project, the system will default to generating a partitioned table, and it is recommended not to make adjustments. When the target data source type is AnalyticDB for PostgreSQL, partitioned tables are not supported. After selecting the input tag, you can configure the code value and code name of the exported tag. You can export the tag value and code name separately or export them all, but at least one must be exported. When one-click creating a table, if the tag has a configured lookup table, you can choose to export the code name. The exported code name is {tag code}_codename. After one-click creating a table, the system will automatically map fields.
   	Date Partition	Select the partition field of the target table. If the selected target table is a partitioned table, the system will default to the first partition field of the table. If the selected target table is a non-partitioned table, there is no need to select a date partition.
   	Partition Field Format	Enter the date format or select an existing date format. You can choose yyyyMMdd, yyyy-MM-dd, yyyy/MM/dd, yyyy.MM.dd. Note Only when the compute engine is MaxCompute, the partition field format can be selected as yyyymmdd, yyyy-mm-dd, yyyy/mm/dd, or yyyy.mm.dd.
   	Loading Policy	Only the overwrite policy is supported. When a primary key or constraint violation occurs, the original data is deleted first, and then the new data row is inserted.
   	Enter Tag	Select the tags to map under the entity, then click the button to configure field mappings.
   	Mapping	Displays the selected tags and their field mapping relationships. Select the mapping field for each output tag. Same name mapping: Click Same Name Mapping to associate tags and their mapping fields with the same name. Purge: Click the icon to purge the mapped relationships. Output content: Select the output content of the tag with a configured lookup table. You can choose tag value and code name. By default, all tag values are selected. You can select tag value and code name at the bottom of the output tag list to select all (entire page).
   Maintenance Configuration	Recurrence	The scheduling cycle for tasks within a specific time range. Daily scheduling is supported. Tag offline tasks run daily at the configured time.

5. Click Publish to complete the creation of the tag offline service task.

Manage tag offline services

1. The tag offline service page displays task name, owner, application name, entity, entity ID, task status, execution status, tag, schedule type, and available operations.

   Hover over the target table to view its full name and data source name. If the data source type is openGauss, you can also view the schema of the target table.

2. (Optional) Filter tasks by selecting Only Show Mine, entering the task name, or using the Filter option to filter by application name, entity-entity ID, target source type, task status, execution status, or schedule type.

3. The Actions column provides the following operations.

   Operation item	Description
   Edit	When the task status is not publishing or unpublishing, click the icon to edit the task on the Edit Offline Service page and republish. The task name, schedule type, target data source type, and loading policy cannot be modified.
   Details	Click the icon to view details of the tag offline service on the View Offline Service page. When the task status is editing, publish failed, published, or offline, click Edit at the bottom of the page to modify the service.
   View instance	Click the icon to view execution instances of the tag offline service.
   Unpublish	When the task status is published or unpublish failed, click the icon to unpublish the tag offline service.
   Data backfill	For recurring schedule tasks with a published status, click the icon to perform data backfill. The default data timestamp for backfill is yesterday's (T-1) data.
   Run	For manual schedule tasks, click the icon to run the task. In the Run dialog box, select the data timestamp.
   Delete	When the task status is offline or publish failed, click the icon to delete the tag offline service.