hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-832) Problem with row keys beginnig with characters < than ',' and the region location cache
Date Fri, 29 Aug 2008 19:09:44 GMT

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

Jean-Daniel Cryans commented on HBASE-832:

bq. Would suggest that tests do actual full HSK compares rather than just row postions.

You mean using compareTo?

bq. Maybe add not to the data member 'tablename' a javadoc that its not serialized as part
of HSK (Point at this issue?).


bq. I should look closer, but does it need to be passed into HSK? Or does HStoreKey.compareTwoRowKeys
not suffice in all cases?

I passed it when the compareTo method was used. Sometimes in the code it was a row comparison,
other times it was a HSK comparison in which I had to make sure that we checked the rows correctly.

bq. If you passed HRI instead of table name to HSK, you could do HRI.isMetatable and HRI.isRoottable
rather than do the table name compares you're currently doing.


> Problem with row keys beginnig with characters < than ',' and the region location
> ---------------------------------------------------------------------------------------
>                 Key: HBASE-832
>                 URL: https://issues.apache.org/jira/browse/HBASE-832
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client, regionserver
>    Affects Versions: 0.2.0
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Blocker
>             Fix For: 0.2.1, 0.18.0
>         Attachments: hbase-832-v1.patch, hbase-832-v2.patch
> We currently have a problem the way we design .META. row keys. When user table row keys
begin with characters lesser than ',' like a '$', any operation will fail when:
> - A client has a certain set of regions in cache
> - One region with the faulty row key splits 
> - The client receives a request for a row in the split region
> The reason is that it will first get a NSRE then it will try to locate a region using
the passed row key. For example: 
> Row in META: entities,,1216750777411
> Row passed: entities,$-94f9386f-e235-4cbd-aacc-37210a870991,99999999999999
> The passed row is lesser then the row in .META.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message