Consider providing error code with exceptions (and documenting them)
--------------------------------------------------------------------
Key: CASSANDRA-3979
URL: https://issues.apache.org/jira/browse/CASSANDRA-3979
Project: Cassandra
Issue Type: Sub-task
Reporter: Sylvain Lebresne
Fix For: 1.1.1
It could be a good idea to assign documented error code for the different
exception raised. Currently, one may have to parse the exception string (say if
one wants to know if its 'create keyspace' failed because the keyspace already
exists versus other kind of exception), but it means we cannot improve the
error message at the risk of breaking client code. Adding documented error
codes with the message would avoid this.
--
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
