[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)

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.0.4
• Component/s: Legacy/Tools
• Severity: Low
• Assignee: Pavel Yaskevich
• Reporter: Matthew F. Dennis

Authors

Pavel Yaskevich

Reviewers

Jonathan Ellis

• Created: 18/Nov/11 21:47
• Updated: 16/Apr/19 09:32
• Resolved: 21/Nov/11 18:26

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"