[
https://issues.apache.org/jira/browse/CASSANDRA-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13154313#comment-13154313
]
Jonathan Ellis commented on CASSANDRA-3508:
-------------------------------------------
I'd be okay with keeping --debug around for that.
> requiring --debug to see stack traces for failures in cassandra-cli is a
> terrible idea (aka silent failure is never a valid option)
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-3508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3508
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 1.0.0
> Reporter: Matthew F. Dennis
> Assignee: Pavel Yaskevich
> Priority: Minor
> Fix For: 1.0.3
>
> Attachments: CASSANDRA-3508.patch
>
>
> this manifests itself in cassandra-cli by returning null to the user. In
> order to see what the problem was (and in many cases, just to know there was
> a problem at all) requires running cassandra-cli with "--debug"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
