CQL console with consistency and tracing

Run CQL with autocomplete, choose consistency per run, trace a query across nodes, and export results to several formats.

The CQL console has a dialect for Cassandra and one for ScyllaDB, with highlighting and autocomplete. Tablyne splits a script into statements and classifies each one as a read, a write or a structure change. That classification drives safe mode and the read-only guard.

The toolbar has the run options. Consistency is chosen for each run. Tablyne never lowers it by itself: if the cluster cannot meet it, the run fails. Serial consistency sets the Paxos phase of conditional writes, those with IF or IF NOT EXISTS. On Amazon Keyspaces, writes are accepted at LOCAL_QUORUM only, and Tablyne says so.

The Trace option runs the statement with tracing and shows each node’s steps, with the coordinator, the duration and the number of events. This is not EXPLAIN. The query actually runs. Tracing reads system_traces, and if the trace does not arrive, Tablyne shows the reason.

Some things are refused with a reason. cqlsh commands such as CONSISTENCY, TRACING and COPY are not CQL, so Tablyne sends none of them and points to the toolbar instead. USE is refused, because it would change the keyspace of every tab on the connection, so write keyspace.table. A BATCH must end with APPLY BATCH. Text Tablyne cannot recognize as CQL is not sent to the server.

Console results are read-only. To edit, open the table tab. Counting rows in a partition reads every row of that partition, and CQL cannot cancel it on the server, so “Stop waiting” only frees the screen.

You can export console results as CSV, JSON, JSONL, Markdown or XLSX. SQL INSERT export is not available for CQL.

ScyllaDB features are available only when the server is proven to be ScyllaDB. They include CDC logs, tablets and local indexes. Some options exist only on Amazon Keyspaces, and Tablyne names the provider when a command does not apply.