cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate McCall (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1862) StorageProxy throws an InvalidRequestException in readProtocol during bootstrap
Date Wed, 15 Dec 2010 17:40:02 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971751#action_12971751
] 

Nate McCall commented on CASSANDRA-1862:
----------------------------------------

I think this is extremely minor (the exception declaration of the method did not change) and
brings us in line with the API as specified in cassandra.thrift: 

IRE:
"Invalid request could mean keyspace or column family does not exist, required parameters
are missing, or a parameter is malformed..."

vs. UE:
"Not all the replicas required could be created and/or read."

> StorageProxy throws an InvalidRequestException in readProtocol during bootstrap
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1862
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1862
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7.0 rc 2
>            Reporter: Nate McCall
>            Assignee: Nate McCall
>            Priority: Minor
>             Fix For: 0.7.0
>
>         Attachments: 1862.txt, 1862_0.6.txt
>
>
> Though the error message provides details, IRE is supposed to signify poorly formed API
requests. In the context of a client request, an UnavailableException is more appropriate.
This would allow the client to take action like removing the node from its host list. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message