MySQL Migration to MAXIR

UDTS supports migration from MySQL to MAXIR. Supported MySQL versions include MySQL (including Percona) 5.5/5.6/5.7/8.x.

1. Functional Limitations

1.1 Source MySQL Limitations

1.1.1 For incremental/full+incremental migration, the source database needs to have binlog enabled with the format set to ROW, and image set to FULL.

Query Method:
show global variables like 'binlog_format';
show global variables like 'binlog_row_image';

Set Method:
set global binlog_format = "ROW" ;
set global binlog_row_image = "FULL" ;

1.1.2 The source tables to be migrated must have a primary key.

1.2 Target MAXIR Limitations

1.2.1 When creating a table in MAXIR, you need to specify DISTRIBUTED BY and CLUSTER BY column attributes, for example:

CREATE TABLE trade (
    id bigint,
    "date" date,
    shopid int NOT NULL,
    sku varchar NOT NULL,
    price decimal(18, 4),
    primary key(date, id)
) DISTRIBUTED BY (id) CLUSTER BY (date, id);

a. CLUSTER BY columns are recommended to be the same as the primary key or part of the primary key, for example, date or {date, id}. b. The column for DISTRIBUTED BY needs to be one of the primary key columns, and it needs to be a column with high cardinality. In this example, it can only be id, not date.

1.2.2 When migrating with UDTS to MAXIR, if the target table does not exist, it will be automatically created. The table creation rules are as follows, and customers need to assess in advance. If they do not meet business requirements, customers can create tables in the target database in advance:

1. CLUSTER BY will be consistent with the table's primary key.
2. DISTRIBUTED BY will use the primary key, and for composite keys, it will use the first field.

2. Migration Content

3. Form Submission

Data Source Form

Transfer Target Form

4. Permissions Requirements

5. Data Type Mapping