[
https://issues.apache.org/jira/browse/ACCUMULO-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840250#comment-13840250
]
John Vines commented on ACCUMULO-1965:
--------------------------------------
While that is great for user facing applications, I do not interpret Accumulo
as that. Accumulo is a backend, and it is more likely for apps to be written
around the accumulo client API. Unless you want to force the checking onto
programmer writing a client, at which point you need to make the method for
validating table names part of the public API. Either method is acceptable to
me, but the former seemed the more straight forward and useful.
> 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)
