Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1312063033.1218747944667.JavaMail.jira@brutus>
Date: Thu, 14 Aug 2008 14:05:44 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-832) Problem with row keys beginnig with
 characters < than ',' and the region location cache
In-Reply-To: <2007237209.1218734984276.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-832:
-----------------------------

If region is a 'meta' region, could we write row keys with a subclass of HSK named something like MetaHSK?  MetaHSK would not treat row as a byte array but instead do simple parse to pull out the tablename and timestamp components.  Remained would be startkey.  Should be possible to then do compare that is not susceptible to changed ordering just because startkey contains delimiter?

Might have to have a version for root and another for meta given that the root has rows made of the meta tables rows.

> Problem with row keys beginnig with characters < than ',' and the region location cache
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-832
>                 URL: https://issues.apache.org/jira/browse/HBASE-832
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.2.0
>            Reporter: Jean-Daniel Cryans
>             Fix For: 0.3.0
>
>
> 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.