hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4921) HTable initialization looks for EMPTY_START_ROW
Date Thu, 01 Dec 2011 03:55:39 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160632#comment-13160632
] 

stack commented on HBASE-4921:
------------------------------

I think you have a case Pritam -- especially if you never get the first region back for whatever
reason.  It would be wrong for locateRegion to return a region that did not 'have' the 'special'
first row so maybe we should be doing something else here when it comes to table operations.
                
> 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

        

Mime
View raw message