我的书签
添加书签
移除书签Cassandra Connector
The Cassandra connector allows querying data stored in Cassandra.
Compatibility
Connector is compatible with all Cassandra versions starting from 2.1.5.
Configuration
To configure the Cassandra connector, create a catalog properties file etc/catalog/cassandra.properties with the following contents, replacing host1,host2 with a comma-separated list of the Cassandra nodes used to discovery the cluster topology:
connector.name=cassandracassandra.contact-points=host1,host2
You will also need to set cassandra.native-protocol-port if your Cassandra nodes are not using the default port (9042).
Multiple Cassandra Clusters
You can have as many catalogs as you need, so if you have additional Cassandra clusters, simply add another properties file to etc/catalog with a different name (making sure it ends in .properties). For example, if you name the property file sales.properties, Presto will create a catalog named sales using the configured connector.
Configuration Properties
The following configuration properties are available:
Property Name | Description |
|---|---|
| Comma-separated list of hosts in a Cassandra cluster. The Cassandra driver will use these contact points to discover cluster topology. At least one Cassandra host is required. |
| The Cassandra server port running the native client protocol (defaults to |
| Consistency levels in Cassandra refer to the level of consistency to be used for both read and write operations. More information about consistency levels can be found in the Cassandra consistency documentation. This property defaults to a consistency level of |
| Set to |
| Username used for authentication to the Cassandra cluster. This is a global setting used for all connections, regardless of the user who is connected to Presto. |
| Password used for authentication to the Cassandra cluster. This is a global setting used for all connections, regardless of the user who is connected to Presto. |
| It is possible to override the protocol version for older Cassandra clusters. This property defaults to |
Note
If authorization is enabled, cassandra.username must have enough permissions to perform SELECT queries on the system.size_estimates table.
The following advanced configuration properties are available:
Property Name | Description |
|---|---|
| Number of rows fetched at a time in a Cassandra query. |
| Number of partitions batched together into a single select for a single partition key column table. |
| Number of keys per split when querying Cassandra. |
| Number of splits per node. By default, the values from the |
| Maximum time the Cassandra driver will wait for an answer to a query from one Cassandra node. Note that the underlying Cassandra driver may retry a query against more than one node in the event of a read timeout. Increasing this may help with queries that use an index. |
| Maximum time the Cassandra driver will wait to establish a connection to a Cassandra node. Increasing this may help with heavily loaded Cassandra clusters. |
| Number of seconds to linger on close if unsent data is queued. If set to zero, the socket will be closed immediately. When this option is non-zero, a socket will linger that many seconds for an acknowledgement that all data was written to a peer. This option can be used to avoid consuming sockets on a Cassandra server by immediately closing connections when they are no longer needed. |
| Policy used to retry failed requests to Cassandra. This property defaults to |
| Set to |
| The name of the local datacenter for |
| Uses the provided number of host per remote datacenter as failover for the local hosts for |
| Set to |
| Set to |
| Set to |
| Set to |
| Comma-separated list of hosts for |
| Retry timeout for |
| The number of speculative executions (defaults to |
| The delay between each speculative execution (defaults to |
| Whether TLS security is enabled (defaults to |
| Path to the PEM or JKS key store. |
| Path to the PEM or JKS trust store. |
| Password for the key store. |
| Password for the trust store. |
Querying Cassandra Tables
The users table is an example Cassandra table from the Cassandra Getting Started guide. It can be created along with the mykeyspace keyspace using Cassandra’s cqlsh (CQL interactive terminal):
cqlsh> CREATE KEYSPACE mykeyspace... WITH REPLICATION = { 'class' : 'SimpleStrategy', 'replication_factor' : 1 };cqlsh> USE mykeyspace;cqlsh:mykeyspace> CREATE TABLE users (... user_id int PRIMARY KEY,... fname text,... lname text... );
This table can be described in Presto:
DESCRIBE cassandra.mykeyspace.users;
Column | Type | Extra | Comment---------+---------+-------+---------user_id | bigint | |fname | varchar | |lname | varchar | |(3 rows)
This table can then be queried in Presto:
SELECT * FROM cassandra.mykeyspace.users;
Data types
The data types mappings are as follows:
Cassandra | Presto |
|---|---|
ASCII | VARCHAR |
BIGINT | BIGINT |
BLOB | VARBINARY |
BOOLEAN | BOOLEAN |
DECIMAL | DOUBLE |
DOUBLE | DOUBLE |
FLOAT | REAL |
INET | VARCHAR(45) |
INT | INTEGER |
LIST<?> | VARCHAR |
MAP<?, ?> | VARCHAR |
SET<?> | VARCHAR |
TEXT | VARCHAR |
TIMESTAMP | TIMESTAMP |
TIMEUUID | VARCHAR |
VARCHAR | VARCHAR |
VARINT | VARCHAR |
SMALLINT | INTEGER |
TINYINT | INTEGER |
DATE | DATE |
Any collection (LIST/MAP/SET) can be designated as FROZEN, and the value is mapped to VARCHAR. Additionally, blobs have the limitation that they cannot be empty.
Types not mentioned in the table above are not supported (e.g. tuple or UDT).
Partition keys can only be of the following types: | ASCII | TEXT | VARCHAR | BIGINT | BOOLEAN | DOUBLE | INET | INT | FLOAT | DECIMAL | TIMESTAMP | UUID | TIMEUUID | SMALLINT | TINYINT | DATE
Limitations
Queries without filters containing the partition key result in fetching all partitions. This causes a full scan of the entire data set, therefore it’s much slower compared to a similar query with a partition key as a filter.
INlist filters are only allowed on index (that is, partition key or clustering key) columns.Range (
<or>andBETWEEN) filters can be applied only to the partition keys.
