accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1965) Invalid table names (& namespaces) should have dedicated error codes
Date Thu, 05 Dec 2013 19:07:36 GMT

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

John Vines commented on ACCUMULO-1965:
--------------------------------------

Actually, looked at the code. Invalid table name presents as an AccumuloException, where as
a null table name or null TimeType present as IllegalArgumentException. This is a good start,
because having ambiguity between not providing a required field vs. having an invalid field
type is an issue. My main gripe currently is that non-existence of a namespace presents as
the exact same error as an invalid table name (as well as conflict with meta table names),
which results in needing to parse error messages in order to disambiguate. There is a similar
issue, though less critical, with namespace creation.

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

Mime
View raw message