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

Pavel Yaskevich commented on CASSANDRA-2630:
--------------------------------------------

Needs rebase but from what I can see from now :

 - in the help "columnfamily" and "keyspace" in describe command should be put 
in <> because those are parameter names
 - NODE_DESCRIBE_TABLE should be changed to NODE_DESCRIBE
 - keyspaceOrcolumnfamily rule is unnecessary
 - there are many grammatical errors and errors in names e.g. "key space", "no 
paramter"
 - indentation problems in describeColumnFamily and executeDescribe methods
 - executeDescribe can be simplified to one if "argument count" = 0; "check if 
authorized to keyspace" -> error || print_keyspace; else "check if argument is 
name of keyspace or column_family" -> print{keyspace/column_family} || error;
 - getKeySpaceDef method should be moved to CliUtils from CliCompiler

> CLI - 'describe column family' would be nice
> --------------------------------------------
>
>                 Key: CASSANDRA-2630
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2630
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jeremy Hanna
>            Assignee: satish babu krishnamoorthy
>            Priority: Minor
>              Labels: cli, lhf
>             Fix For: 1.0
>
>         Attachments: cassandra-0.8.2-2630-1.txt, cassandra-0.8.2-2630.txt
>
>
> I end up verifying column families a lot and using 'describe keyspace 
> <keyspace>;' spits out a whole bunch of data since our keyspace has a lot of 
> metadata.  It would be really useful to have a 'describe <column family>;' 
> for a given column family in the currently authenticated keyspace.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to