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

Pritam Damania updated HBASE-4921:
----------------------------------

    Description: 
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.

  was:
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.

    
> 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
>            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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to