tencent cloud

Tencent Cloud WeData

Release Notes
Dynamic Release Record (2026)
Product Introduction
Product Overview
Product Advantages
Product Architecture
Product Features
Application Scenarios
Purchase Guide
Billing Overview
Product Version Purchase Instructions
Execute Resource Purchase Description
Billing Modes
Overdue Policy
Refund
Preparations
Overview of Account and Permission Management
Add allowlist /security groups (Optional)
Sign in to WeData with Microsoft Entra ID (Azure AD) Single Sign-On (SSO)
Operation Guide
Console Operation
Project Management
Data Integration
Studio
Data Development
Data Analysis
Data Science
Data Governance (with Unity Semantics)
API Documentation
History
Introduction
API Category
Making API Requests
Smart Ops Related Interfaces
Project Management APIs
Resource Group APIs
Data Development APIs
Data Asset - Data Dictionary APIs
Data Development APIs
Ops Center APIs
Data Operations Related Interfaces
Data Exploration APIs
Asset APIs
Metadata Related Interfaces
Task Operations APIs
Data Security APIs
Instance Operation and Maintenance Related Interfaces
Data Map and Data Dictionary APIs
Data Quality Related Interfaces
DataInLong APIs
Platform Management APIs
Data Source Management APIs
Data Quality APIs
Platform Management APIs
Asset Data APIs
Data Source Management APIs
Data Types
Error Codes
WeData API 2025-08-06
Service Level Agreements
Related Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Conversion Node Configuration

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2024-11-01 17:33:23
Offline synchronization supports three types of data nodes: input, output, and transformation.

String Replacement

The string replacement node mainly uses Java regular expressions to match and replace the content of string fields. This node will perform the replacement operation when the string is partially or completely matched in the field content. The configuration parameters for conversion rules are as follows:
Parameter
Description
Field
Select the field to match the string. The fields processed by this node must be of string type.
Note:
In this conversion node, multiple conversion rules can be configured for the same field. Multiple rules will be serialized according to the configuration order.
Regular expression
Java regular expression used to match the original field content.
New string
Replace the matched field content with the specified new string.
Replacement method
Supports replacing only the first match or all matches.
Delete
Delete this row rule.

Time format conversion

The time format conversion node is mainly used to convert the time field in the table to the target format, such as converting yyyymmdd time format to yyyymmdd hh:mm:ss format. The conversion rule parameters are as follows:
Parameter
Description
Field
Select the field that needs to match the time format. The field should be of types such as datetime, time, timestamp, date, etc.
Note:
In this conversion node, multiple conversion rules can be configured for the same field.
Source time format
Specify the time format for this field. If the specified format does not match the actual format, the conversion will not be performed, and the data will be processed as dirty data.
Target time format
For each record, if the current field matches the specified source target format, the system will convert the source time format to the target format.
Delete
Delete this row rule.
Note
Currently, this node only supports offline synchronization tasks.

Value Conversion

The value conversion node is mainly used for standardized processing of field content. This node will perform a replacement operation when the field content is exactly equal to the specified content. After the replacement, the original field content will be updated. For example, "CHINA" will be uniformly replaced with "CHN". The conversion rule parameters are as follows:
Parameter
Description
Field
Select the field that needs time format matching. Fields are by default sourced from upstream fields, and all upstream fields are supported.
Note:
In this conversion node, multiple conversion rules can be configured for the same field.
Matching Value
Used to determine if the original field is equal to the specified value. If equal, the replacement behavior will replace the value.
Replacement Value
Value conversion target, cannot be empty.
Delete
Delete this row rule.
Note
Currently, this node only supports offline synchronization tasks.


도움말 및 지원

문제 해결에 도움이 되었나요?

피드백