[ https://issues.apache.org/jira/browse/CASSANDRA-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448848#comment-13448848 ]
Sylvain Lebresne commented on CASSANDRA-3979: --------------------------------------------- Actually, on the "add the extra info to thrift", it's a tad more complicated that I though partly because thrift exception don't always have a message. Typically InvalidRequestException have one but not UnavailableException, nor TimeoutException. So do we want to bother adding a new optional message to those exceptions to serialize the exception code and added informations this patch adds? > 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