cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Updated) (JIRA)" <j...@apache.org>
Subject [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)
Date Fri, 18 Nov 2011 22:14:52 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-3508:
--------------------------------------

          Component/s: Tools
             Priority: Minor  (was: Major)
    Affects Version/s:     (was: 1.0.1)
             Assignee: Pavel Yaskevich
    
> 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
>            Reporter: Matthew F. Dennis
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>
> 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

        

Mime
View raw message