-
Notifications
You must be signed in to change notification settings - Fork 66
Supported databases
Yongjoo Park edited this page Jul 25, 2018
·
1 revision
- CDH 5.7 / Impala 2.5 or later
- Spark 2.0 or later
- MySQL 5.5 or later
- Redshift
- PostgreSQL 10 or later
TODO:
- Hive
- Oracle
- SQL Server
| Supported Data Types | Not Supported |
|---|---|
| BIT, BOOL, SMALLINT, MEDIUMINT, INT, INTEGER, BIGINT, DECIMAL, DEC, FLOAT, DOUBLE, DOUBLE PRECISION, DATE, DATETIME, TIMESTAMP, TIME, YEAR, CHAR, VARCHAR, BINARY, VARBINARY, TINYBLOB, TINYTEXT, BLOB, TEXT, MEDIUMBLOB, MEDIUMTEXT, LONGBLOB, LONGTEXT, ENUM, SET |
| Supported Data Types | Not Supported |
|---|---|
| SMALLINT, INT2, INTEGER, INT, INT4, BIGINT, DECIMAL, NUMERIC, REAL, FLOAT4, DOUBLE PRECISION, FLOAT8, FLOAT, BOOLEAN, BOOL, CHAR, CHARACTER, CHARACTER VARYING, NVARCHAR, TEXT, DATE, TIMESTAMP, TIMESTAMP WITHOUT TIME ZONE | TIMESTAMPTZ, TIMESTAMP WITH TIME ZONE |
| Supported Data Types | Not Supported |
|---|---|
| BIGINT, BITSERIAL, BIT, VARBIT, BOOLEAN, BOX, BYTEA, CHAR, VARCHAR, CIDR, CIRCLE, DATE, FLOAT8, INET, INTEGER, JSON, LINE, LSEG, MACADDR, MACADDR8, MONEY, NUMERIC, PATH, POINT, POLYGON, REAL, SMALLINT, SMALLSERIAL, SERIAL, TEXT, TIME, TIMESTAMP, UUID, BIT VARYING, INT8, BOOL, CHARACTER, CHARACTER VARYING, INT, INT4, DOUBLE PRECISION, DECIMAL, FLOAT, INT2, SERIAL2, SERIAL4, TIMETZ, TIMESTAMPTZ, SERIAL8 | XML |
Note for Impala:
The main syntax consideration is the column order in the PARTITIONED BY clause and the select list: the partition key columns must be listed last in the select list, in the same order as in the PARTITIONED BY clause. Therefore, in this case, the column order in the destination table is different from the source table. You also only specify the column names in the PARTITIONED BY clause, not the data types or column comments.