Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 17 Apr 2015 07:36:59 +0000 (UTC)
From: "Anoop Sam John (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12821789.1429255905000.27474.1429256219127@Atlassian.JIRA>
In-Reply-To: <JIRA.12821789.1429255905000@Atlassian.JIRA>
References: <JIRA.12821789.1429255905000@Atlassian.JIRA>
 <JIRA.12821789.1429255905195@arcas>
Subject: [jira] [Updated] (HBASE-13491) Issue in
 FuzzyRowFilter#getNextForFuzzyRule
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-13491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anoop Sam John updated HBASE-13491:
-----------------------------------
    Affects Version/s: 1.0.0

> Issue in FuzzyRowFilter#getNextForFuzzyRule
> -------------------------------------------
>
>                 Key: HBASE-13491
>                 URL: https://issues.apache.org/jira/browse/HBASE-13491
>             Project: HBase
>          Issue Type: Bug
>          Components: Filters
>    Affects Versions: 1.0.0
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>         Attachments: HBASE-13491.patch
>
>
> {code}
> for (int i = 0; i < result.length; i++) {
>       if (i >= fuzzyKeyMeta.length || fuzzyKeyMeta[i] == 1) {
>         result[i] = row[offset + i];
>         if (!order.isMax(row[i])) {
>           // this is "non-fixed" position and is not at max value, hence we can increase it
>           toInc = i;
>         }
>       }
> {code}
> See we take row bytes with out considering the row offset.  The test cases are passing as we pass 0 offset row bytes. Change in the test will reveal the bug.
> Came across this when I was working on HBASE-11425


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