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

Josh Elser edited comment on ACCUMULO-2087 at 12/24/13 3:03 AM:
----------------------------------------------------------------

This gets really nasty, really fast. [~ctubbsii], is this just a hole in the 
implementation? As I'm working through this, it just looks like concurrent 
table/namespace operations weren't even considered, as such, the API is just 
throwing stuff constantly and there's overlap between what should be a table 
related error and a namespace related error.

Edit: for example, take {{o.a.a.s.c.ServerConfiguration#getTableConfiguration}} 
calls {{getNamespaceConfigurationForTable}} which makes a 
{{TableParentConfiguration}} (still not sure what that actually is supposed to 
do) which ultimately tries to get the namespace for a table ID (which could 
fail). That entire chain either needs to propagate a TableNotFoundException or 
a NamespaceNotFound exception, both of which don't really make sense in 
portions of that call stack.


was (Author: elserj):
This gets really nasty, really fast. [~ctubbsii], is this just a hole in the 
implementation? As I'm working through this, it just looks like concurrent 
table/namespace operations weren't even considered, as such, the API is just 
throwing stuff constantly and there's overlap between what should be a table 
related error and a namespace related error.

> Tables.getNamespaces NPE's on missing table ID
> ----------------------------------------------
>
>                 Key: ACCUMULO-2087
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2087
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Critical
>             Fix For: 1.6.0
>
>
> If the user provides a tableID which doesn't exist to getNamespace, the 
> implementation will NPE if a table with that ID doesn't exist.
> It should throw a proper exception and be noted in the javadoc as such.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to