Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 19 Jun 2015 10:10:00 +0000 (UTC)
From: "Anoop Sam John (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12838775.1434630396000.118914.1434708600936@Atlassian.JIRA>
In-Reply-To: <JIRA.12838775.1434630396000@Atlassian.JIRA>
References: <JIRA.12838775.1434630396000@Atlassian.JIRA>
 <JIRA.12838775.1434630396692@arcas>
Subject: [jira] [Commented] (HBASE-13933) DBE's seekBefore with tags
 corrupts the tag's offset information thus leading to incorrect results
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Anoop Sam John commented on HBASE-13933:
----------------------------------------

+1. Good find.

{code}
 if (encoding == DataBlockEncoding.PREFIX_TREE) {
321	      // TODO : Fix this
322	      assertEquals(null, scanner.getKeyValue());
323	    } else {
324	      assertEquals("k", toRowStr(scanner.getKeyValue()));
325	    }
{code}
Now you don't need this in the test.  Is this another bug with PREFIX_TREE?  Have any Jira?

> DBE's seekBefore with tags corrupts the tag's offset information thus leading to incorrect results
> --------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-13933
>                 URL: https://issues.apache.org/jira/browse/HBASE-13933
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.0.0, 2.0.0, 1.0.1, 1.1.0, 0.98.13, 1.0.1.1, 1.1.0.1
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Critical
>             Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.1, 1.3.0
>
>         Attachments: HBASE-13933.patch, HBASE-13933_2.patch, HBASE-13993_1.patch
>
>
> The problem occurs with moveToPrevious() case and incase of tags we copy the previous pointer's tag info to the current because already decoded the tags.
> Will check once again before I post other details.  I have a test case to reproduce the problem. Found this while working with MultibyteBuffers and verified if this is present in trunk - it is in all branches where we have tags compression (I suppose) will verify


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)