You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/06/29 22:09:00 UTC

[jira] [Resolved] (HBASE-18022) Refine the error message issued with TableNotFoundException when expected table is not the same as the one fetched from meta

     [ https://issues.apache.org/jira/browse/HBASE-18022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-18022.
---------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed

Pushed to master and to branch-2. Thanks for the patch [~waterlx]

> Refine the error message issued with TableNotFoundException when expected table is not the same as the one fetched from meta
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-18022
>                 URL: https://issues.apache.org/jira/browse/HBASE-18022
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Xiang Li
>            Assignee: Xiang Li
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HBASE-18022.master.000.patch
>
>
> Regarding the following error message
> bq. ERROR: java.io.IOException: org.apache.hadoop.hbase.TableNotFoundException: Table 'hbase:acl' was not found, got: table1.
> It is not clear. Users have no idea what it means and have to check the code and find that it is issued by ConnectionImplementation#locateRegionInMeta() when the table inputted is not the same as the one fetched from meta.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)