You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2013/12/05 17:30:35 UTC

[jira] [Commented] (ACCUMULO-1965) Invalid table names (& namespaces) should have dedicated error codes

    [ https://issues.apache.org/jira/browse/ACCUMULO-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840235#comment-13840235 ] 

Christopher Tubbs commented on ACCUMULO-1965:
---------------------------------------------

Following the guidelines in "Effective Java", this type of error seems to be of the "programmer error" type, and as such, I think a RuntimeException with an informative error message is perfectly acceptable (so long as the message gets propagated to the client).

> 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)