Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <16894327.174301280985496970.JavaMail.jira@thor>
Date: Thu, 5 Aug 2010 01:18:16 -0400 (EDT)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Updated: (HBASE-2823) Entire Row Deletes not stored in
 Row+Col Bloom
In-Reply-To: <5444306.267311278620809482.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-2823:
-------------------------

          Status: Resolved  (was: Patch Available)
    Hadoop Flags: [Reviewed]
    Release Note:   (was: Just a minor fix)
      Resolution: Fixed

Committed.  Thanks for the patch Alexander Georgiev.

> Entire Row Deletes not stored in Row+Col Bloom
> ----------------------------------------------
>
>                 Key: HBASE-2823
>                 URL: https://issues.apache.org/jira/browse/HBASE-2823
>             Project: HBase
>          Issue Type: Bug
>          Components: filters, regionserver
>    Affects Versions: 0.90.0
>            Reporter: Nicolas Spiegelberg
>            Assignee: Alexander Georgiev
>             Fix For: 0.90.0
>
>         Attachments: HBASE-2823.patch, HBASE-2823.patch
>
>
> If the user issues a Row Delete on an family with Row+Col blooms, that information is not currently detected by shouldSeek().  Possible known solutions are:
> 1. adding Row as Bloom Filter Key on Row Delete, shouldSeek() should do both a Row & Row+Col query for Row+Col filters.
> 2. keep delete information in a separate storage element.
> #1 seems like the best solution, but need to investigate further and fix this problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.