[jira] [Updated] (HBASE-20719) HTable.batch() doesn't handle TableNotFound correctly.

["Guanghao Zhang (JIRA)" <ji...@apache.org>]

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

Guanghao Zhang updated HBASE-20719:
-----------------------------------
    Fix Version/s:     (was: 2.2.0)
                   2.3.0

> HTable.batch() doesn't handle TableNotFound correctly.
> ------------------------------------------------------
>
>                 Key: HBASE-20719
>                 URL: https://issues.apache.org/jira/browse/HBASE-20719
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 2.1.0
>            Reporter: Sergey Soldatov
>            Assignee: Sergey Soldatov
>            Priority: Minor
>             Fix For: 2.3.0
>
>
> batch() as well as delete() are processing using AsyncRequest. To report about problems we are using RetriesExhaustedWithDetailsException and there is no special handling for TableNotFound exception. So, the final result for running batch or delete operations against not existing table looks really weird and missleading:
> {noformat}
> hbase(main):003:0> delete 't1', 'r1', 'c1'
> 2018-06-12 15:02:50,742 ERROR [main] client.AsyncRequestFutureImpl: Cannot get replica 0 location for {"totalColumns":1,"row":"r1","families":{"c1":[{"qualifier":"","vlen":0,"tag":[],"timestamp":9223372036854775807}]},"ts":9223372036854775807}
> ERROR: Failed 1 action: t1: 1 time, servers with issues: null
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)