Documentation

Cassandra

Connect TableR to Apache Cassandra over CQL with contact points, keyspace, optional authentication and SSL/TLS, verifying the connection, and troubleshooting.

Cassandra is a wide-column store reached over CQL. Point TableR at one or more contact points and, if the cluster requires it, add credentials.

Overview

TableR connects to a Cassandra cluster using the CQL native protocol (default port 9042). You can give one or more contact points; the driver discovers the rest of the cluster. A keyspace scopes the tables you browse.

  • Cluster — connect to one or more contact points on port 9042.
  • Auth — a cluster username is required; a password when the cluster enforces it.
  • Keyspace — optional scope for the tables you browse (the Database field).

Before you start

  • One or more reachable contact points (host and port).
  • A cluster username — this is required.
  • The user's password, if the cluster enforces authentication.
  • Optionally, a keyspace and the local datacenter name.
  • For remote clusters: network access to the port and, usually, SSL/TLS.

Connection fields

These defaults match TableR's Cassandra connection form. Secrets are written to the operating system keyring, never to plain configuration files.

FieldRequiredDefaultNotes
HostYes127.0.0.1One or more contact points (comma-separated).
PortYes9042The CQL native protocol port.
UsernameYesThe cluster user used to authenticate.
PasswordNoOptional; required when the cluster enforces auth. Stored in the OS keyring.
KeyspaceNoOptional (the Database field); scopes browsing to one keyspace.
DatacenterNoOptional local datacenter name for routing.
SSL/TLSNoOffEnable for remote clusters.

Connect with the form

  1. 1
    Choose Cassandra

    Open the launcher and pick the Cassandra card.

  2. 2
    Enter contact points and port

    Use 127.0.0.1 and 9042 locally, or your cluster's hosts.

  3. 3
    Add credentials

    Type the username, and the password if the cluster requires it.

  4. 4
    Set a keyspace (optional)

    Use the Database field to scope browsing to one keyspace.

  5. 5
    Set the datacenter (optional)

    Provide the local datacenter name for routing.

  6. 6
    Enable SSL/TLS for remote

    Turn on SSL/TLS when connecting to a remote cluster.

  7. 7
    Save and connect

    Save the profile so it reappears in the launcher, then connect.

SSL/TLS

Local clusters usually need no encryption. For a remote cluster, enable SSL/TLS so credentials and data are protected in transit.

  • Off — no encryption (local or trusted networks only).
  • On — encrypt the connection to the cluster.
  • Enable it for any remote or managed cluster.

Verify the connection

Once connected, open a query tab and run CQL against the system keyspace:

SELECT release_version FROM system.local;
SELECT cluster_name FROM system.local;

If both statements return a row, the connection and credentials are working.

Troubleshooting

SymptomLikely causeFix
All host(s) tried for query failedNo reachable contact point, wrong port, or a firewall.Confirm at least one contact point is up and 9042 is reachable.
Authentication errorWrong username or password.Re-check the credentials and update the saved password (it lives in the keyring).
Keyspace does not existThe Keyspace field names a missing keyspace.Leave Keyspace empty, or enter one that exists.
No host available in datacenterWrong local datacenter name.Re-check the Datacenter value, or leave it blank.

Next steps