Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Wed, 10 Apr 2013 09:52:15 +0000 (UTC)
From: "chunhui shen (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12641800.1365587533967.141633.1365587535452@arcas>
In-Reply-To: <JIRA.12641800.1365587533967@arcas>
References: <JIRA.12641800.1365587533967@arcas>
Subject: [jira] [Created] (HBASE-8317) Seek returns wrong result with
 PREFIX_TREE Encoding
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

chunhui shen created HBASE-8317:
-----------------------------------

             Summary: Seek returns wrong result with PREFIX_TREE Encoding
                 Key: HBASE-8317
                 URL: https://issues.apache.org/jira/browse/HBASE-8317
             Project: HBase
          Issue Type: Bug
    Affects Versions: 0.95.0
            Reporter: chunhui shen
            Assignee: chunhui shen


TestPrefixTreeEncoding#testSeekWithFixedData from the patch could reproduce the bug.

An example of the bug case:
Suppose the following rows:

1.row3/c1:q1/
2.row3/c1:q2/
3.row3/c1:q3/
4.row4/c1:q1/
5.row4/c1:q2/

After seeking the row 'row30', the expected peek KV is row4/c1:q1/, but actual is row3/c1:q1/.


I just fix this bug case in the patch, 

Maybe we can do more for other potential problems if anyone is familiar with the code of PREFIX_TREE


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira