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 2016/11/16 21:03:59 UTC

[jira] [Resolved] (HBASE-4921) HTable initialization looks for EMPTY_START_ROW

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

stack resolved HBASE-4921.
--------------------------
    Resolution: Cannot Reproduce

Resolving as no longer relevant.

> HTable initialization looks for EMPTY_START_ROW
> -----------------------------------------------
>
>                 Key: HBASE-4921
>                 URL: https://issues.apache.org/jira/browse/HBASE-4921
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.4, 0.95.2
>            Reporter: Pritam Damania
>
> The HTable initialization does something like this : 
> {code}this.connection.locateRegion(tableName, HConstants.EMPTY_START_ROW);{code}
> What is the rationale behind this ? What would happen if this region is in flight ? I ran into a problem where I disabled the first region of the table and now I can't create an HTable instance to this table.
> Disabling the first region is like disabling the entire table from a client perspective. I feel this is not the correct behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)