The following table lists the Cassandra data types supported by the driver and how they are mapped to JDBC data types.

The complex types List, Map, Set, Tuple, and user-defined types have no direct JDBC mapping. However, the driver normalizes these types to provide SQL access to Cassandra. For details on how complex types are mapped, see "Complex Type Normalization."

See "getTypeInfo()" for getTypeInfo() results of data types supported by the driver.

Table 1. Data Type Mapping
Apache Cassandra JDBC
ASCII VARCHAR
BIGINT BIGINT
BLOB LONGVARBINARY
BOOLEAN BOOLEAN
COUNTER 1 BIGINT
DATE 2 DATE
DECIMAL DECIMAL
DOUBLE DOUBLE
DURATION 3 VARCHAR
FLOAT REAL
INET VARCHAR
INT INTEGER
LIST 4 LONGVARCHAR
MAP 5 LONGVARCHAR
SET 6 LONGVARCHAR
SMALLINT 7 SMALLINT
TIME 8 TIME
TIMESTAMP TIMESTAMP
TIMEUUID CHAR
TINYINT 9 TINYINT
TUPLE 10 LONGVARCHAR
USERTYPE 11 LONGVARCHAR
UUID CHAR
VARCHAR VARCHAR
VARINT DECIMAL
1 Update is supported for Counter columns when all the other columns in the row comprise that row’s primary key. See Update for details.
2 Supported for Apache Cassandra 2.2 and higher.
3 Currently, the Duration type is supported only in simple columns, and not in Collection types.
4 See Complex Type Normalization for details on how complex types are mapped.
5 See Complex Type Normalization for details on how complex types are mapped.
6 See Complex Type Normalization for details on how complex types are mapped.
7 Supported for Apache Cassandra 2.2 and higher.
8 Supported for Apache Cassandra 2.2 and higher.
9 Supported for Apache Cassandra 2.2 and higher.
10 See Complex Type Normalization for details on how complex types are mapped.
11 Also referred to as user-defined types. These are data types created with the CQL CREATE TYPE statement. See Complex Type Normalization for details on how Usertype is mapped.