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 Mon, 03 Sep 2012 10:28:07 GMT


Sylvain Lebresne commented on CASSANDRA-3979:

bq. 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?

That was the reason I was conservative initially here. But if we're willing to break the super-fragile
clients, I'm absolutely good doing that. 
> 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