You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matthew F. Dennis (Updated) (JIRA)" <ji...@apache.org> on 2011/11/18 22:48:52 UTC
[jira] [Updated] (CASSANDRA-3508) requiring --debug to see stack
traces for failures in cassandra-cli is a terrible idea (aka silent failure
is never a valid option)
[ https://issues.apache.org/jira/browse/CASSANDRA-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew F. Dennis updated CASSANDRA-3508:
-----------------------------------------
Description: 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"
> 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
> Affects Versions: 1.0.1
> Reporter: Matthew F. Dennis
>
> 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