cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Splinter (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-11032) Full trace returned on ReadFailure
Date Tue, 19 Jan 2016 18:26:39 GMT
Chris Splinter created CASSANDRA-11032:
------------------------------------------

             Summary: Full trace returned on ReadFailure
                 Key: CASSANDRA-11032
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11032
             Project: Cassandra
          Issue Type: Bug
          Components: Tools
            Reporter: Chris Splinter
            Priority: Minor


I noticed that the full traceback is returned on a read failure where I expected this to be
a one line exception with the ReadFailure message. It is minor, but would it be better to
only return the ReadFailure details?

{code}
cqlsh> SELECT * FROM test_encryption_ks.test_bad_table;
Traceback (most recent call last):
  File "/usr/local/lib/dse/bin/../resources/cassandra/bin/cqlsh.py", line 1276, in perform_simple_statement
    result = future.result()
  File "/usr/local/lib/dse/resources/cassandra/bin/../lib/cassandra-driver-internal-only-3.0.0-6af642d.zip/cassandra-driver-3.0.0-6af642d/cassandra/cluster.py",
line 3122, in result
    raise self._final_exception
ReadFailure: code=1300 [Replica(s) failed to execute read] message="Operation failed - received
0 responses and 1 failures" info={'failures': 1, 'received_responses': 0, 'required_responses':
1, 'consistency': 'ONE'}
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message