Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 6 Aug 2015 20:17:09 +0000 (UTC)
From: "Vishy Kasar (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12852681.1438892197000.394291.1438892229273@Atlassian.JIRA>
In-Reply-To: <JIRA.12852681.1438892197000@Atlassian.JIRA>
References: <JIRA.12852681.1438892197000@Atlassian.JIRA>
 <JIRA.12852681.1438892197740@arcas>
Subject: [jira] [Created] (CASSANDRA-10009) Surface KeyspaceNotPresent as a
 specific exception code
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Vishy Kasar created CASSANDRA-10009:
---------------------------------------

             Summary: 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
             Fix For: 2.0.x


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)