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