You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Pavel Yaskevich (JIRA)" <ji...@apache.org> on 2011/01/18 18:09:45 UTC
[jira] Assigned: (CASSANDRA-1565) cassandra-cli use consistant
flags and improve error messages
[ https://issues.apache.org/jira/browse/CASSANDRA-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Yaskevich reassigned CASSANDRA-1565:
------------------------------------------
Assignee: Pavel Yaskevich
> cassandra-cli use consistant flags and improve error messages
> -------------------------------------------------------------
>
> Key: CASSANDRA-1565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1565
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Environment: Centos 5 using http://mirror.lividpenguin.com/pub/apache//cassandra/0.7.0/apache-cassandra-0.7.0-beta1-bin.tar.gz
> Reporter: Ian Rogers
> Assignee: Pavel Yaskevich
> Priority: Minor
> Fix For: 0.8
>
> Attachments: trunk-1565.txt
>
>
> nodetool uses "-h" to specify the host to connect to but cassandra-cli uses "-host" which is a pain to remember.
> More importantly, if you do use "-h" then there's no error! If you do this and then try to "show keyspaces" or some such you just get an entirely accurate though confusing "not connected to a cluster" error.
> 1. Make the flags consistant amongst all the tools where appropriate.
> 2. If you supply a flag to a tool it doesn't recognise then the tool should error immediately and display its usage message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.