MySQL Configuration
MySQL parameters are used to customize rules for MySQL and BigQuery script migration.
Open the features-mysql.properties file in the config folder and configure Parameters in the features-mysql.properties file as required.
|
Parameter |
Description |
Value Range |
Default Value |
Example |
|---|---|---|---|---|
|
Whether to use a database name as the schema name. If a database name does not exist, the user-defined schema specified by table.schema will be used. If table.schema is not specified, the default schema will be used. |
|
|
|
|
Name of the user-defined schema. If this parameter is specified, it will be directly used. In this case, even if useDatabaseAsSchema is set to true, the name of the current schema will be used. |
|
|
|
|
Default data storage mode. Value ROW means row storage, and value COLUMN means column storage. |
|
|
|
|
Default table type, which can be partitioned table, replication table, or round-robin table. REPLICATION, HASH, and ROUND-ROBIN |
|
|
|
|
Tablespace options |
|
|
|
|
Policy for selecting the partition key |
|
|
|
|
Partition key. If this parameter is not specified, the default selection policy will be used. If there are multiple columns, separate them with commas (,). The column names are case insensitive. |
|
|
|
|
Compression mode. If keyword COMPRESS is specified in CREATE TABLE, the compression feature will be triggered in the case of bulk INSERT operations. If this feature is enabled, a scan will be performed on all tuple data within the page to generate a dictionary and then the tuple data will be compressed and stored. If NOCOMPRESS is used, tables will not be compressed. |
|
|
|
|
Compression level of table data. It determines the compression ratio and duration. |
||||
|
Table data compression ratio and duration at the same compression level. This divides a compression level into sublevels, providing more choices for the compression ratio and duration. As the value becomes larger, the compression ratio becomes higher and duration longer at the same compression level. |
|
|
|
|
Database template |
|
|
table.database.template=template0 |
|
A database code. |
|
|
table.database.encoding=UTF8 |
|
Whether to rename an index during its creation. |
|
|
table.index.rename=false |
|
Whether all non-aggregated columns in a SELECT statement are included in the GROUP BY clause. |
|
|
table.database.onlyFullGroupBy=true |
|
This parameter allows you to convert the REAL data type. By default, it is set to false, which means that the data type is converted to DOUBLE PRECISION. However, if you set it to true, the data type will be converted to REAL. |
|
|
table.database.realAsFloat=false |
|
Whether to add GROUP BY to the having clause. |
|
|
table.database.havingAddGroupBy=true |
|
Whether the UUID function is output as the original statement function.
The default value is false. |
|
|
table.function.uuid=false |
|
Split function.
|
|
|
table.function.split=true |
|
Whether the try_cast function is output as the original statement function.
|
|
|
table.function.tryCast=false |
|
Whether the setNames statement is commented out and is not converted.
|
|
|
table.sql.set.names=true |
|
Whether the setPassword statement is commented out and is not converted.
|
|
|
table.sql.set.password=true |
|
Whether the setResourceGroup statement is commented out and is not converted.
|
|
|
table.sql.set.resource.group=true |
|
Whether the setRole statement is commented out and is not converted.
|
|
|
table.sql.set.role=true |
|
Whether the setVariable statement is commented out and is not converted.
|
|
|
table.sql.set.variable=true |
|
Conversion type of the SQL file. The value can be ddl or plsql. The default value is ddl. When a stored procedure or user-defined function is executed, plsql is used. |
|
|
sql.conversion.type=ddl |
|
How to handle primary key or unique index conflicts during insertion.
|
|
|
table.insert.convert.upsert=false |
|
Whether to support the ALTER TABLE... ADD INDEX conversion. false (default value): The conversion is not supported. true: The conversion is supported. |
|
|
table.alter.add.index=false |
|
Whether to comment out redundant constraints. false (default value): The redundant constraints are not commented out. |
|
|
table.create.comment.constraint=false |
|
Whether to include the "check" constraint for the set type. false (default value): The constraint is not included. |
|
|
table.create.type.set=false |
|
Whether to include the "in not null" constraint for the enum type. false (default value): The constraint is not included. |
|
|
table.create.type.enum=false |
|
Whether to convert column fields to lowercase. true (default value): The column fields are converted to lowercase. false: The uppercase and lowercase letters are the same as those in the original SQL statement. |
|
|
table.create.columnCase=true |
|
Version of the column-store format. The value can be 1.0, 2.0 (default value), or 3.0. |
|
|
table.option.colversion=2.0 |
|
Source database type. The value can be bigquery, doris, synapse, or mysql&adb. The default value is mysql&adb. |
|
|
table.origin.database.type = mysql |
|
Specifies whether to allow HStore tables. The value can be true or false. The default value is null. The value false indicates that hstore is set to false in the statement. |
|
|
table.enable.hstore= |
|
Whether to allow the hstore_opt operation. true: The operation is allowed. false: The operation is not allowed. |
|
|
table.enable.hstore.opt=true |
|
Whether to output the original SQL statement of the partition as a comment. The value can be true or false. |
|
|
table.partition.comment.enable=false |
|
Whether to combine the type name with the schema name during type creation. The value can be true or false. |
|
|
table.type.schema.prefix=true |
|
The partition_expiration_days parameter needs to be converted to an integer, so the rounding rule needs to be specified.
|
|
|
table.option.partition.ttl=HALF_UP |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot