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
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.
