You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2015/08/06 22:42:06 UTC
[jira] [Resolved] (CASSANDRA-10009) Surface KeyspaceNotPresent as a
specific exception code
[ https://issues.apache.org/jira/browse/CASSANDRA-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Stupp resolved CASSANDRA-10009.
--------------------------------------
CASSANDRA-9202 will introduce the concept of error codes.
Just adding a new response code to the protocol is not possible without breaking existing clients (and the spec). So the feature of _error codes_ will be introduced in a future C* version and be available to clients using the then to be introduced version (and specification) of the native protocol.
> Surface KeyspaceNotPresent as a specific exception code
> -------------------------------------------------------
>
> Key: CASSANDRA-10009
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10009
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Vishy Kasar
>
> When key space is not present, the server sends back an exception code of INVALID. The underlying reason is buried in the exception message. We have specific use cases where we want to retry KeyspaceNotPresent exception. However only way to achieve this today is to parse the exception message which is not good. Please surface KeyspaceNotPresent as a specific exception code
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)