[jira] Updated: (CASSANDRA-807) Improve cassandra-cli error display and thrift connection checking

["Mark Wolfe (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Wolfe updated CASSANDRA-807:
---------------------------------

    Attachment: cassandra-cli-cleanup.patch

The attached file contains changes based on this issue as well as:
* More internal java doc for methods in this area
* A bit of a tidy up of code in the classes which were modified 
* Removal of some redundant code which wasn't used


> Improve cassandra-cli error display and thrift connection checking
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-807
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-807
>             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 name
> * 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.