[
https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681667#comment-16681667
]
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:
{noformat}
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.
...
{noformat}
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: https://issues.apache.org/jira/browse/CASSANDRA-14825
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
