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

Sylvain Lebresne commented on CASSANDRA-8005:
---------------------------------------------

I'm not entirely sure what you intend by this, but I'd rather just do 
CASSANDRA-6717 and call it a day. Basically, CASSANDRA-6717 is about making the 
schema table be a much more direct representation of the CQL schema, which will 
remove the complexity for drivers/cqlsh.

Now, I'm not sure what you intend this server-side {{DESCRIBE}} to return, but 
if it's a string, then I don't think this is any more helpful for drivers as 
they would have to parse that string (and assuming CASSANDRA-6717, reading 
schema table will be a lot simpler). So I'm tempted to say that CASSANDRA-6717 
should solve the problems expressed here, but I might be missing some of you 
points.

> Server-side DESCRIBE
> --------------------
>
>                 Key: CASSANDRA-8005
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8005
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API
>            Reporter: Tyler Hobbs
>            Priority: Minor
>              Labels: cql3
>             Fix For: 3.0
>
>
> The various {{DESCRIBE}} commands are currently implemented by cqlsh, and 
> nearly identical implementations exist in many drivers.  There are several 
> motivations for making {{DESCRIBE}} part of the CQL language:
> * Eliminate the (fairly complex) duplicate implementations across drivers and 
> cqlsh
> * Get closer to allowing drivers to not have to fetch the schema tables. 
> (Minor changes to prepared statements are also needed.)
> * Have instantaneous support for new schema features in cqlsh.  (You 
> currently have to update the bundled python driver.)
> * Support writing out schemas where it makes sense.  One good example of this 
> is backups.  You need to restore the schema before restoring data in the case 
> of total loss, so it makes sense to write out the schema alongside snapshots.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to