You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2017/02/03 05:30:51 UTC

[jira] [Commented] (ACCUMULO-4577) Getting namespaceId using tableId when table deleted throws wrong expection

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

Christopher Tubbs commented on ACCUMULO-4577:
---------------------------------------------

The subject is a bit misleading. The method itself isn't necessarily throwing the wrong exception. A deleted table id is an illegal argument for this method. The problem is that, due to how the utility method is used, the wrong exception gets propagated to the user.

> Getting namespaceId using tableId when table deleted throws wrong expection
> ---------------------------------------------------------------------------
>
>                 Key: ACCUMULO-4577
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4577
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.7.2, 1.8.0
>            Reporter: Keith Turner
>            Assignee: Michael Miller
>             Fix For: 1.7.3, 1.8.1, 2.0.0
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> While working on ACCUMULO-4575 I noticed that {{Tables.getNamespaceId(String tableId)}} has odd behavior.  When the table is not found, it throws an illegal argument exception.  In many cases what should happen in this case is that a ThriftTableNotFound exception should be thrown.  Doing this will cause clients to get a clean TableNotFound exception instead of an internal server error message.
> One possible solution is to make this method throw TableNotFoundException and also offer a new method that wraps, catches TableNotFoundException and throws ThriftTableNotFound.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)