Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 057FA10E76 for ; Thu, 5 Dec 2013 19:23:36 +0000 (UTC) Received: (qmail 25440 invoked by uid 500); 5 Dec 2013 19:23:35 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 25408 invoked by uid 500); 5 Dec 2013 19:23:35 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 25399 invoked by uid 99); 5 Dec 2013 19:23:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Dec 2013 19:23:35 +0000 Date: Thu, 5 Dec 2013 19:23:35 +0000 (UTC) From: "Sean Busbey (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1965) Invalid table names (& namespaces) should have dedicated error codes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840448#comment-13840448 ] Sean Busbey commented on ACCUMULO-1965: --------------------------------------- bq. My main gripe currently is that non-existence of a namespace presents as the exact same error as an invalid table name Shouldn't this use NamespaceNotFoundException ? > Invalid table names (& namespaces) should have dedicated error codes > -------------------------------------------------------------------- > > Key: ACCUMULO-1965 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1965 > Project: Accumulo > Issue Type: Bug > Components: client > Reporter: John Vines > > To improve the client API, we should minimize the number of exceptions that require String parsing to determine the exception type. Table naming errors is one of them. -- This message was sent by Atlassian JIRA (v6.1#6144)