Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 6 Jul 2012 19:37:34 +0000 (UTC)
From: "Ahmet AKYOL (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <2059118652.15556.1341603454517.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1131542904.3064.1339432063144.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (CASSANDRA-4330) cqlsh's desc cluster needs to
 return the schema agreement information
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ahmet AKYOL commented on CASSANDRA-4330:
----------------------------------------

One related thing is that both Cqlsh's "DESC KEYSPACE" and cli's "show schema" commands continue to show dropped tables. Moreover, Cqlsh's very nifty autocomplete feature also shows dropped table names. I guess this is related to CFs in system keyspace. I like to see these issues solved.

Thanks in advance...
                
> 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
>            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