cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Wolfe (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-807) Improve cassandra-cli error display and thrift connection checking
Date Mon, 22 Feb 2010 09:04:27 GMT


Mark Wolfe updated CASSANDRA-807:

    Attachment: cassandra-cli-cleanup.patch

Updated patch which has the following:
- Nailed all the brace layout issues in the files I touched making these changes.
- Corrected the comment relating to retrieval of cluster name in the connect method. Initially
I used it to test the connection, then came to the conclusion that displaying this similar
to mysql / oracle would be handy.

> Improve cassandra-cli error display and thrift connection checking
> ------------------------------------------------------------------
>                 Key: CASSANDRA-807
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>         Environment: Java
>            Reporter: Mark Wolfe
>         Attachments: cassandra-cli-cleanup.patch
> A new user observed that thier was some ambiguous error messages presented by the cassandra
CLI if you connected to the wrong port on the cassandra daemon, or in fact anything else listening
for a tcp connection. The CLI will say "connected" but when you run any of the commands a
thrift exception will be displayed.
> So I suggest the following enhancements:
> * Verify that the CLI is indeed connected to a thrift port by requesting the cluster
> * Hide as many of the stack traces as possible displaying a simple error message
> * Implement a --debug argument to the CLI which will output stacktraces

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message