Introduction
...
Teradata Data Type | CDAP Schema Data Type | Support | Comment |
|---|---|---|---|
BYTEINT | Schema.Type.INT | + | |
SMALLINT | Schema.Type.INT | + | |
INTEGER | Schema.Type.INT | + | |
BIGINT | Schema.Type.LONG | + | |
DECIMAL/NUMERIC | Schema.LogicalType.DECIMAL | + | |
FLOAT/REAL/DOUBLE PRECISION | Schema.Type.DOUBLE | + | |
NUMBER | Schema.LogicalType.DECIMAL | + | |
BYTE | Schema.Type.BYTES | + | |
VARBYTE | Schema.Type.BYTES | + | |
| BLOB | Schema.Type.BYTES | + | |
CHAR | Schema.Type.STRING | + | |
VARCHAR | Schema.Type.STRING | + | |
| CLOB | Schema.Type.STRING | + | |
DATE | Schema.Type.DATE | + | |
TIME | Schema.LogicalType.TIME_MICROS | + | |
TIMESTAMP | Schema.LogicalType.TIMESTAMP_MICROS | + | |
TIME WITH TIME ZONE | Schema.LogicalType.TIME_MICRO | + | |
TIMESTAMP WITH TIME ZONE | Schema.LogicalType.TIMESTAMP_MICROS | + | |
INTERVAL YEAR | Schema.Type.STRING | + | |
INTERVAL YEAR TO MONTH | Schema.Type.STRING | + | |
INTERVAL MONTH | Schema.Type.STRING | + | |
INTERVAL DAY | Schema.Type.STRING | + | |
INTERVAL DAY TO HOUR | Schema.Type.STRING | + | |
INTERVAL DAY TO MINUTE | Schema.Type.STRING | + | |
INTERVAL DAY TO SECOND | Schema.Type.STRING | + | |
INTERVAL HOUR | Schema.Type.STRING | + | |
INTERVAL HOUR TO MINUTE | Schema.Type.STRING | + | |
INTERVAL HOUR TO SECOND | Schema.Type.STRING | + | |
INTERVAL MINUTE | Schema.Type.STRING | + | |
INTERVAL MINUTE TO SECOND | Schema.Type.STRING | + | |
INTERVAL SECOND | Schema.Type.STRING | + | |
PERIOD(DATE) | |||
PERIOD(TIME) | |||
PERIOD(TIME WITH TIME ZONE) | |||
PERIOD(TIMESTAMP) | |||
PERIOD(TIMESTAMP WITH TIME ZONE) | |||
| JSON | |||
| SET | |||
| ARRAY | - | ||
| XML | - | ||
ST_Geometry | |||
MBR |
Approach
Create a module teradata-plugin in database-plugins project, reuse existing database-plugins code if possible. Add Teradata-specific properties to configuration, add support for Teradata-specific data types. Update UI widgets JSON definitions.
...