Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A4B6B10092 for ; Wed, 11 Sep 2013 13:43:08 +0000 (UTC) Received: (qmail 56995 invoked by uid 500); 11 Sep 2013 13:43:08 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 56848 invoked by uid 500); 11 Sep 2013 13:43:03 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 56552 invoked by uid 99); 11 Sep 2013 13:43:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Sep 2013 13:43:01 +0000 Date: Wed, 11 Sep 2013 13:43:00 +0000 (UTC) From: "Chao Shi (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-9444) EncodedScannerV2#isSeeked does not behave as described in javadoc MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-9444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764304#comment-13764304 ] Chao Shi commented on HBASE-9444: --------------------------------- bq. will it be better to ask seeker whether it is being seeked to? Agree that with the current code, checking the seeker object to not null will work. But which one will look cleaner? I don't quite understand: in current code, the seeker is lazily initialized, so I don't have a chance to ask it for whether been seekd. Plus that there are already several EncodedSeeker implementations in the codebase, so I think it better not to add a new method. > EncodedScannerV2#isSeeked does not behave as described in javadoc > ----------------------------------------------------------------- > > Key: HBASE-9444 > URL: https://issues.apache.org/jira/browse/HBASE-9444 > Project: HBase > Issue Type: Bug > Components: HFile > Reporter: Chao Shi > Priority: Minor > Attachments: hbase-9444.patch > > > I hit this when my tool is scanning HFiles using the scanner. I found isSeeked behaves different whether the HFiles are prefix-encoded or not. > There is a test case in my patch that demonstrates the bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira