소식 및 공지 사항

릴리스 노트

제품 소개

제품 개요

데이터 마이그레이션 기능 설명

데이터 동기화 기능 설명

데이터 구독(Kafka 버전) 기능 설명

제품 장점

구매 가이드

과금 개요

환불 설명

시작하기

데이터 마이그레이션 작업 가이드

데이터 동기화 작업 가이드

데이터 구독 작업 가이드(Kafka 버전)

준비 작업

자체구축 MySQL용 Binlog 설정

데이터 마이그레이션

데이터 마이그레이션 지원 데이터베이스

ApsaraDB 교차 계정 인스턴스 간 마이그레이션

PostgreSQL로 마이그레이션

작업 관리

데이터 동기화

데이터 동기화가 지원하는 데이터베이스

계정 간 TencentDB 인스턴스 동기화

작업 관리

데이터 구독(Kafka 버전)

데이터 구독이 지원하는 데이터베이스

데이터 구독 작업 생성

작업 관리

컷오버 설명

모니터링 및 알람

모니터링 메트릭 조회

사례 튜토리얼

양방향 동기화 데이터 구조 생성

다대일 동기화 데이터 구조 생성

멀티 사이트 Active-Active IDC 구축

데이터 동기화 충돌 해결 정책 선택하기

CLB 프록시를 사용하여 계정 간 데이터베이스 마이그레이션하기

CCN으로 자체 구축 MySQL에서 TencentDB for MySQL로 마이그레이션

검증 불통과 처리 방법

버전 확인

원본 데이터베이스 권한 확인

계정 충돌 확인

부분 데이터베이스 매개변수 확인

원본 인스턴스 매개변수 확인

매개변수 설정 충돌 확인

대상 데이터베이스 콘텐츠 충돌 확인

대상 데이터베이스 공간 확인

Binlog 매개변수 확인

증분 마이그레이션 전제 조건 확인

플러그인 호환성 확인

레벨2 파티션 테이블 확인

기본 키 확인

마이그레이션할 테이블에 대한 DDL 확인

시스템 데이터베이스 충돌 확인

소스 및 대상 인스턴스 테이블 구조 확인

InnoDB 테이블 확인

마이그레이션 객체 종속성 확인

제약 조건 확인

FAQs

데이터 마이그레이션

데이터 동기화

데이터 구독 Kafka 버전 FAQ

구독 정규식

API문서

History

Introduction

API Category

Making API Requests

(NewDTS) Data Migration APIs

Data Sync APIs

Data Consistency Check APIs

(NewDTS) Data Subscription APIs

Data Types

Error Codes

DTS API 2018-03-30

Service Agreement

Service Level Agreements

액세스 관리

DTS를 사용할 서브 계정 생성 및 권한 부여

서브 계정에 재무 권한 부여하기

JSON Demo Description

포커스 모드

폰트 크기

마지막 업데이트 시간: 2025-02-12 16:45:08

The demo for each programming language uses JSON for serialization and contains a Record definition file.
In the demo for Java, the path of the definition file is consumerDemo-json-java\\src\\main\\java\\json\\FlatRecord.java.
‍Type of Field in Record
Field Name in Record
Description
id
The globally incremental ID
version
The protocol version, which is v1 currently.
messageType
The message type. Enumerated values: "INSERT", "UPDATE", "DELETE", "DDL", "BEGIN", "COMMIT", "HEARTBEAT", "CHECKPOINT".
fileName
The name of the binlog file where the current record is located
position
The end offset of the current record in the binlog in the format of End_log_pos@binlog file number. For example, if the current record is in file mysql-bin.000004 and the end offset is 2196, then the value of this parameter will be 2196@4.
safePosition
The start offset of the current transaction in the binlog, which is in the same format as described above.
timestamp
The time when the data was written to the binlog, which is a UNIX timestamp in seconds.
gtid
The current GTID, such as c7c98333-6006-11ed-bfc9-b8cef6e1a231:9.
transactionId
The transaction ID, which is generated only for COMMIT events.
serverId
The server ID of the source database, which can be viewed by running SHOW VARIABLES LIKE 'server_id'.
threadId
The ID of the session that committed the current transaction, which can be viewed by running SHOW processlist;.
sourceType
The source database type, which currently can only be MySQL.
sourceVersion
The source database version, which can be viewed by running:
 select version();.
schemaName
Database name
tableName
Table name
objectName
Format: Database name.table name
columns
The definitions of columns in the table
oldColumns
The data of the row before DML execution. If the message is an INSERT message, the array will be null.
newColumns
The data of the row after DML execution. If the message is a DELETE message, the array will be null.
sql
The DDL SQL statement
executionTime
The DDL execution duration in seconds
heartbeatTimestamp
The timestamp of the heartbeat message in seconds. This field is present only for heartbeat messages.
syncedGtid
The collection of GTIDs parsed by DTS in the format of c7c98333-6006-11ed-bfc9-b8cef6e1a231:1-13
fakeGtid
Whether the current GTID is forged. If gtid_mode is not enabled, DTS will forge a GTID.
pkNames
If the table in the source database has a primary key, this parameter will be carried in the DML message; otherwise, it will not be carried.
readerTimestamp
The time when DTS processed the current data record, which is a UNIX timestamp in milliseconds.
tags
The status_vars in QueryEvent. For more information, see QueryEvent.
total
The total number of message segments if the message is segmented. This field is invalid on the current version (version=1) and is reserved for extension.
index
The index of message segments if the message is segmented. This field is invalid on the current version (version=1) and is reserved for extension.
MySQL Column Attribute in Record
name: The column name.
dataTypeNumber: The type of the data recorded in the binlog. For values, see MySQL source code documentation.
isKey: Whether the current key is the primary key.
originalType: The type defined in DDL.
MySQL Data Type Conversion Logic
In the JSON protocol, all MySQL data types are converted to strings.
String types such as varchar are all converted to UTF-8 encoding.
Numeric types are all converted to strings equal to the value, such as "3.0".
Time types are output in the format of YYYY-MM-DD HH:mm:ss.SSS.
Timestamp types are output as the number of milliseconds.
Binary types such as binary and blob are output as strings equal to their hex values, such as "0xfff".

도움말 및 지원

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

더 자세한 내용은 문의하기 또는 티겟 제출 을 통해 문의할 수 있습니다.

피드백

tencent cloud

Data Transfer Service

JSON Demo Description

‍Type of Field in Record

MySQL Column Attribute in Record

MySQL Data Type Conversion Logic

도움말 및 지원

Field Name in Record	Description
id	The globally incremental ID
version	The protocol version, which is v1 currently.
messageType	The message type. Enumerated values: "INSERT", "UPDATE", "DELETE", "DDL", "BEGIN", "COMMIT", "HEARTBEAT", "CHECKPOINT".
fileName	The name of the binlog file where the current record is located
position	The end offset of the current record in the binlog in the format of `End_log_pos@binlog file number`. For example, if the current record is in file `mysql-bin.000004` and the end offset is 2196, then the value of this parameter will be `2196@4`.
safePosition	The start offset of the current transaction in the binlog, which is in the same format as described above.
timestamp	The time when the data was written to the binlog, which is a UNIX timestamp in seconds.
gtid	The current GTID, such as c7c98333-6006-11ed-bfc9-b8cef6e1a231:9.
transactionId	The transaction ID, which is generated only for COMMIT events.
serverId	The server ID of the source database, which can be viewed by running `SHOW VARIABLES LIKE 'server_id'`.
threadId	The ID of the session that committed the current transaction, which can be viewed by running `SHOW processlist;`.
sourceType	The source database type, which currently can only be MySQL.
sourceVersion	The source database version, which can be viewed by running: `select version();`.
schemaName	Database name
tableName	Table name
objectName	Format: Database name.table name
columns	The definitions of columns in the table
oldColumns	The data of the row before DML execution. If the message is an INSERT message, the array will be null.
newColumns	The data of the row after DML execution. If the message is a DELETE message, the array will be null.
sql	The DDL SQL statement
executionTime	The DDL execution duration in seconds
heartbeatTimestamp	The timestamp of the heartbeat message in seconds. This field is present only for heartbeat messages.
syncedGtid	The collection of GTIDs parsed by DTS in the format of `c7c98333-6006-11ed-bfc9-b8cef6e1a231:1-13`
fakeGtid	Whether the current GTID is forged. If `gtid_mode` is not enabled, DTS will forge a GTID.
pkNames	If the table in the source database has a primary key, this parameter will be carried in the DML message; otherwise, it will not be carried.
readerTimestamp	The time when DTS processed the current data record, which is a UNIX timestamp in milliseconds.
tags	The `status_vars` in `QueryEvent`. For more information, see QueryEvent.
total	The total number of message segments if the message is segmented. This field is invalid on the current version (version=1) and is reserved for extension.
index	The index of message segments if the message is segmented. This field is invalid on the current version (version=1) and is reserved for extension.