[ 
https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681660#comment-16681660
 ] 

Jeremiah Jordan commented on CASSANDRA-14825:
---------------------------------------------

Wether we add DESCRIBE or we have a virtual table or even both, we return data 
in result sets.  If you want to be able to query the whole schema in a single 
query I can think of two reasonable options:
1. Return a single row and column that just has the entire schema in it.
2. Return one row per schema object with columns something like: keyspace, 
name, type, cql

The current patch here proposes a different table per object type. I don’t 
think that is as usable as a being able to get a single result set with all 
schema objects in it. You require multiple querys and the user has to know how 
to put them back together in the right order to generate a valid schema cql 
file for use in a restore.  With a single row containing the whole schema it 
can be in the right order or with a single resultset for all objects the rows 
can be returned in the correct order for replay.

> 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

Reply via email to