[
https://issues.apache.org/jira/browse/CASSANDRA-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444605#comment-13444605
]
paul cannon commented on CASSANDRA-3979:
----------------------------------------
+1 on this monster. This will be fantastic for clients, and should encourage
use of the binary protocol. I did have to make a really small change to the
'stress' tool code to get a full successful build, as shown here:
https://github.com/thepaul/cassandra/commit/7b1f71f6 , but that's a triviality.
The only other thing is that it would have been nice to include the extra
information for Thrift clients too- even if it's just rendered into the error
string. But maybe that would break super-fragile clients that depend on exact
error messages?
> 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
> Components: API
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Labels: cql3
> Fix For: 1.2.0 beta 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
