[CASSANDRA-807] Improve cassandra-cli error display and thrift connection checking

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 0.6
• Component/s: Legacy/Tools
• Labels: cli

Environment

Java

• Assignee: Mark Wolfe
• Reporter: Mark Wolfe

Authors

Mark Wolfe

• Created: 17/Feb/10 21:17
• Updated: 16/Apr/19 09:33
• Resolved: 24/Feb/10 00:42

Description

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