Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Sat, 11 Apr 2015 00:38:14 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12432944.1250145265000.60342.1428712694580@Atlassian.JIRA>
In-Reply-To: <JIRA.12432944.1250145265000@Atlassian.JIRA>
References: <JIRA.12432944.1250145265000@Atlassian.JIRA>
 <JIRA.12432944.1250145265722@arcas>
Subject: [jira] [Resolved] (HBASE-1764) Change hfile scanner seek to find
 wanted key or the one AFTER rather than BEFORE as it currently does
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell resolved HBASE-1764.
-----------------------------------
    Resolution: Not A Problem

> Change hfile scanner seek to find wanted key or the one AFTER rather than BEFORE as it currently does
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1764
>                 URL: https://issues.apache.org/jira/browse/HBASE-1764
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: stack
>
> Working on new getClosestAtOrBefore in HBASE-1761, the way hfile scanner works where it gets the asked for key or the one just before makes for our doing more work than we should.   See the code in Store where we want to get to first element in row.  We have to go to the row before and then walk forward skipping the item that is in row before.
> Consider flipping catalog tables to be regions by end-key rather than start-key at same time (RE: conversation had on the saturday night at the SUSF hackathon).


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