Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 21 Nov 2011 18:04:51 +0000 (UTC)
From: "Pavel Yaskevich (Updated) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <2086709834.51907.1321898691697.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <74997965.45078.1321652932245.JavaMail.tomcat@hel.zones.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)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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