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 8EF5710022 for ; Thu, 5 Dec 2013 20:03:39 +0000 (UTC) Received: (qmail 11051 invoked by uid 500); 5 Dec 2013 20:03:38 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 11016 invoked by uid 500); 5 Dec 2013 20:03:38 -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 10974 invoked by uid 99); 5 Dec 2013 20:03:38 -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 20:03:38 +0000 Date: Thu, 5 Dec 2013 20:03:38 +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=13840505#comment-13840505 ] Sean Busbey commented on ACCUMULO-1965: --------------------------------------- bq. It should, but then it's an API change. This is all going in 1.6.0, right? I thought we made API changes across major versions? bq. That was why I suggested that NamespaceNotFound/Exists/NotEmpty should all extend AccumuloException to get around those issues Code written against the create table API in 1.5 couldn't have known about namespaces. If we're making API change decisions with an eye towards making said code work in a mixed environment, extending AccumuloException would be a reasonable way to do that. The reviewboard feedback you mention looks mostly ambivalent. Maybe this particular set of implications is worth its own ticket+patch or a mailing list thread? > 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)