[
https://issues.apache.org/jira/browse/ACCUMULO-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840331#comment-13840331
]
John Vines commented on ACCUMULO-1965:
--------------------------------------
Valid table names aren't quite the same as null arguments. We should provide a
utility for checking because users shouldn't depend on constants.valid table
regex.
Then, if they still fail, it could be an illegal argument exception or a typed
exception (but never just a runtime exception) . And an illegal argument
exception should be fine because that's the only real argument to create table.
So either solution should work, but it seems like we should have a table name
check utility available to users in the client api.
> 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)
