Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 6 Oct 2011 20:15:30 +0000 (UTC)
From: "Nicolas Spiegelberg (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <126500584.4966.1317932130543.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1823631131.7347.1316799746741.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4469) Avoid top row seek by looking up
 bloomfilter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Nicolas Spiegelberg commented on HBASE-4469:
--------------------------------------------

+1. lgtm
                
> Avoid top row seek by looking up bloomfilter
> --------------------------------------------
>
>                 Key: HBASE-4469
>                 URL: https://issues.apache.org/jira/browse/HBASE-4469
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Liyin Tang
>            Assignee: Liyin Tang
>
> The problem is that when seeking for the row/col in the hfile, we will go to top of the row in order to check for row delete marker (delete family). However, if the bloomfilter is enabled for the column family, then if a delete family operation is done on a row, the row is already being added to bloomfilter. We can take advantage of this factor to avoid seeking to the top of row.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira