[
https://issues.apache.org/jira/browse/CASSANDRA-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
paul cannon resolved CASSANDRA-4330.
------------------------------------
Resolution: Won't Fix
Turns out this is not of much use in 1.1, post "schema renaissance", and the
information is no longer in the system.Schema table (since the system.schema_*
tables are now canonical), so we can't do it via plain CQL. Cqlsh does still
use thrift for certain things, but I'd like to move toward eliminating those,
rather than adding to it just for 1.0 when cassandra-cli can meet the need
acceptably.
http://www.datastax.com/dev/blog/the-schema-management-renaissance has good
explanations of the changes.
> cqlsh's desc cluster needs to return the schema agreement information
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-4330
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4330
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jeremy Hanna
> Assignee: paul cannon
> Priority: Minor
> Labels: cli, cqlsh
>
> describe cluster in the cassandra cli is very useful to determine whether the
> schema for the cluster is in complete agreement among the nodes. It doesn't
> appear that the cqlsh analog - desc cluster; - does the same thing.
> Since that's so useful and since cqlsh is the way forward for new cli type of
> development, it makes sense to add that in some command in cqlsh. Paul said
> that it should be trivial but if it's not, it may be worth it to wait until
> the dedicated cql transport to implement it (while it's still there in
> cassandra-cli).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
