Data Type Mapping

The table below shows how each upstream MySQL column type maps to a Doris column type. There is a single mapping, shared by both sync methods — the only difference is who creates the target table:

• Auto Table Creation Sync: Doris reads the upstream schema and creates the target table with these Doris column types automatically.
• SQL Mapping Sync: you create the target table yourself, using a compatible Doris type for each column.

In both cases, the values are written following the same mapping. For types that are not supported, see Limitations.

MySQL to Doris

MySQL Type	Doris Type	Notes
BOOLEAN / TINYINT(1)	BOOLEAN
TINYINT	TINYINT	UNSIGNED → SMALLINT
SMALLINT	SMALLINT	UNSIGNED → INT
MEDIUMINT	INT	UNSIGNED → INT
INT	INT	UNSIGNED → BIGINT
BIGINT	BIGINT	UNSIGNED → LARGEINT
YEAR	SMALLINT
FLOAT	FLOAT
DOUBLE	DOUBLE
DECIMAL(p,s)	DECIMAL(p,s)	Very high precision falls back to STRING
DATE	DATE
DATETIME	DATETIME(s)	Microsecond scale (0–6) preserved
TIMESTAMP	DATETIME(s)	Normalized to the server time zone
TIME	STRING	Serialized as a string, e.g. 12:34:56.000000
CHAR	CHAR
VARCHAR	VARCHAR
TINYTEXT / TEXT / MEDIUMTEXT / LONGTEXT	STRING
BINARY / VARBINARY / TINYBLOB / BLOB / MEDIUMBLOB / LONGBLOB	STRING	Base64-encoded string
BIT(1)	BOOLEAN
BIT(n>1)	STRING	Base64-encoded string
JSON	STRING	Stored as JSON text
ENUM	STRING	Resolved to the label value
SET	STRING	Resolved to comma-separated labels
Spatial types (GEOMETRY, POINT, …) and other types	Not supported	Auto Table Creation fails for tables with such columns; use SQL Mapping Sync (cast in SELECT) or exclude the column