cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (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 Mon, 21 Nov 2011 18:04:51 GMT

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

Pavel Yaskevich updated CASSANDRA-3508:
---------------------------------------

    Attachment: CASSANDRA-3508-v2.patch

this patch keeps the --debug option and shows exceptions in the places your mentioned only
when that option is set.
                
> 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-v2.patch, 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

        

Mime
View raw message