[
https://issues.apache.org/jira/browse/CASSANDRA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051209#comment-13051209
]
Rick Shaw commented on CASSANDRA-2477:
--------------------------------------
So from the client side you will need to know the name of the Keyspace and the
names of the CFs where this data will be stored and updated by the server. And
the server side will need to fully document the current schema description of
the CF(s) to do the SELECT on. And keep the CFs updated with any additions and
updates to the internal KS and CF metadata. But with that info in hand the
client could just issue a SELECT of the involved CF to get the metadata that is
currently held in the internal server metadata structures represented by the
associated KS/CFs. Is that the plan?
> CQL support for describing keyspaces / column familes
> -----------------------------------------------------
>
> Key: CASSANDRA-2477
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2477
> Project: Cassandra
> Issue Type: Sub-task
> Components: API, Core
> Reporter: Eric Evans
> Labels: cql
> Fix For: 0.8.2
>
> Attachments: 2477-virtual-cfs-false-start.txt
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
