cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14825) Expose table schema for drivers
Date Fri, 09 Nov 2018 16:29:00 GMT


Sylvain Lebresne commented on CASSANDRA-14825:

To maybe clarify/be more precise, when I say "promote the DESCRIBE syntax cqlsh supports to
proper CQL", what I have in mind is that each `DESCRIBE` statement would return a result set
with only one result, but there would many variants, so:
DESCRIBE SCHEMA;         // returns a single string with the whole schema
DESCRIBE KEYSPACE ks; // returns a single string, with all of keyspace 'ks'
DESCRIBE TABLE ks.t       // returns a single string with just that one table.
Again, I think it's going much more messy to get something approaching that flexibility with
tables (doable, sure, but more messy).

> Expose table schema for drivers
> -------------------------------
>                 Key: CASSANDRA-14825
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Chris Lohfink
>            Assignee: Chris Lohfink
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
> Currently the drivers recreate the CQL for the tables by putting together the system
table values. This is very difficult to keep up to date and buggy enough that its only even
supported in Java and Python drivers. Cassandra already has some limited output available
for snapshots that we could provide in a virtual table or new query that the drivers can fetch.
This can greatly reduce the complexity of drivers while also reducing bugs like CASSANDRA-14822
as the underlying schema and properties change.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message