cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3979) Consider providing error code with exceptions (and documenting them)
Date Wed, 05 Sep 2012 16:08:08 GMT


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:
>             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:

View raw message