Loading
How Aerospike's Architecture and Data Types Correspond to Presto's
Aerospike and Presto have different data architectures. They also support different data types. The following tables show how the Aerospike architecture corresponds to Presto's, and how the data types they support correspond to each other.
Aerospike's architecture versus Presto's architecture
| Aerospike | Presto |
|---|---|
| cluster | catalog |
| namespace | schema |
| set | table |
| record | row |
| bin | column |
Data types in Aerospike versus data types in Presto
info
The Presto connector does not support all Presto data types. You must typecast unsupported types to supported types.
| Aerospike Data Type | Presto Data Type |
|---|---|
| byte[] | VARBINARY |
| String | VARCHAR |
| Integer | INTEGER |
| Long | BIGINT |
| Double | DOUBLE |
| Float | DOUBLE |
| Boolean (see note) | BOOLEAN |
| Byte | TINYINT |
| Value.ListValue | JSON |
| Value.MapValue | JSON |
| Value.GeoJSONValue | JSON |
| Value.HLLValue | HYPER_LOG_LOG |
Note: The Boolean data type is supported in versions 1.1.0 and later of Aerospike Connect for Presto, and requires version 5.6 or later of Aerospike Database Enterprise Edition.