You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2008/08/14 21:43:44 UTC
[jira] Issue Comment Edited: (HBASE-832) Problem with row keys
beginnig with characters < than ',' and the region location cache
[ https://issues.apache.org/jira/browse/HBASE-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622657#action_12622657 ]
apurtell edited comment on HBASE-832 at 8/14/08 12:42 PM:
----------------------------------------------------------------
Of the set of bytes < ',' '$' and '*' are commonly used for special keys in various applications. '!' is a possibility also.
Why not use the space character instead of comma?
was (Author: apurtell):
Of the set of bytes < ',' '$' and '*' are commonly used for special keys in various operations. '!' is a possibility also.
Why not use the space character instead of comma?
> 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.