[ https://issues.apache.org/jira/browse/CASSANDRA-8005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153816#comment-14153816 ]
Jonathan Ellis commented on CASSANDRA-8005: ------------------------------------------- Why is every driver implementing describe in the first place? In my mind, once CASSANDRA-6717 is done it should be very simple for a driver to give a list of tables, columns in that table, etc. Which is NOT the same as reverse engineering that into a CREATE TABLE statement, which is a job for cqlsh. Drivers shouldn't need to reinvent that part. (Opscenter might, but I'm okay with that. :)) > 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)