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

Aleksey Yeschenko commented on CASSANDRA-8005:
----------------------------------------------

I don't feel as strongly about this as I used to (used to be extremely against 
it), but I'm still not completely convinced.

What we do want from drivers (or, at least, what we already have in the 
drivers, and will have to keep there, as Sylvain says) - is the programmatic 
access to the metadata. And getting CREATE statements from there is more or 
less trivial (more so once CASSANDRA-6717 is in, which is soon).

Once(?) OPSC moves to the python-driver, it will also no longer have to 
reinvent this logic, and use the driver's. And for CASSANDRA-7190 we don't 
really need a DESCRIBE statement in CQL.

CASSANDRA-7660 + CASSANDRA-6171 is what we really want/need.

> 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