[
https://issues.apache.org/jira/browse/CASSANDRA-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837769#action_12837769
]
Hudson commented on CASSANDRA-807:
----------------------------------
Integrated in Cassandra #364 (See
[http://hudson.zones.apache.org/hudson/job/Cassandra/364/])
less confusing handling of errors/exceptions
* replaces some printed exceptions with human readable error messages,
while re-enabling the printed exceptions if --debug is passed.
* pull cluster name property on connect or startup, and output, (this
also forces any connection errors to occur sooner).
Patch by Mark Wolfe; reviewed by eevans for
> 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
> Assignee: Mark Wolfe
> Fix For: 0.6
>
> 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.
