Connecting ScyllaDB through the Cassandra integration
The editor, the object browser and every CQL type read back identically, and the panels that go quiet do so because one virtual keyspace is not there.
6 posts
Writing on Cassandra
CQL editor with keyspace, table and type introspection for wide-column data. Where it stops: No joins and no EXPLAIN — the grid respects partition-key query rules instead of hiding them.
CQL has no EXPLAIN, so the tab is hidden
The keyword is not in the grammar at all, and the only alternative profiles a statement that has already run, which is not a plan and is not offered as one.
Three Cassandra panels refuse rather than report a zero
Table, index and storage statistics send no statement at all and carry the measurement behind the refusal, because no honest count or size exists to publish.
The Cassandra field no other connection asks for
The driver refuses to build a load-balancing policy without a local data centre, which is why that field sits in the open rather than under Advanced.
Paging CQL, and the running statement you cannot stop
A second page is refused with its reason rather than silently re-serving the first, and there is no cancel path at all on this engine to fall back on.
No constraints to discover, and a column order to rebuild
The catalog reports no position for regular columns and sorts by name, so the tree rebuilds the order a where clause actually needs.