hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Yates (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-4921) HTable initialization looks for EMPTY_START_ROW
Date Thu, 30 Aug 2012 15:33:08 GMT

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

Jesse Yates updated HBASE-4921:

    Affects Version/s: 0.96.0
> 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.96.0
>            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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message