cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-8005) Server-side DESCRIBE
Date Tue, 14 Apr 2015 17:43:14 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-8005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-8005.
---------------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 3.0)

> 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: client-impacting, cql3
>
> 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)

Mime
View raw message