Return-Path: 
 <issues-return-33334-apmail-hbase-issues-archive=hbase.apache.org@hbase.apache.org>
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 A22979A5C
	for <apmail-hbase-issues-archive@www.apache.org>;
 Mon, 23 Jan 2012 17:55:02 +0000 (UTC)
Received: (qmail 5938 invoked by uid 500); 23 Jan 2012 17:55:02 -0000
Delivered-To: apmail-hbase-issues-archive@hbase.apache.org
Received: (qmail 5885 invoked by uid 500); 23 Jan 2012 17:55:01 -0000
Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@hbase.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@hbase.apache.org>
List-Post: <mailto:issues@hbase.apache.org>
List-Id: <issues.hbase.apache.org>
Delivered-To: mailing list issues@hbase.apache.org
Received: (qmail 5876 invoked by uid 99); 23 Jan 2012 17:55:01 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jan 2012 17:55:01 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jan 2012 17:55:00 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id A91E515E2A3
	for <issues@hbase.apache.org>; Mon, 23 Jan 2012 17:54:40 +0000 (UTC)
Date: Mon, 23 Jan 2012 17:54:40 +0000 (UTC)
From: "Alex Newman (Updated) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1361813346.67506.1327341280694.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <742441057.61321.1327090720355.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HBASE-5240) HBase internalscanner.next javadoc
 doesn't imply whether or not results are appended or not
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-5240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Newman updated HBASE-5240:
-------------------------------

    Status: Patch Available  (was: Open)
    
> HBase internalscanner.next javadoc doesn't imply whether or not results are appended or not
> -------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5240
>                 URL: https://issues.apache.org/jira/browse/HBASE-5240
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Alex Newman
>            Assignee: Alex Newman
>         Attachments: 0001-HBASE-5240.-HBase-internalscanner.next-javadoc-doesn.patch
>
>
> Just looking at http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/regionserver/InternalScanner.html. We don't know whether or not the results are appended to results list, or if we always clear it first.
> boolean 	next(List<KeyValue> results)
>           Grab the next row's worth of values.
>  boolean 	next(List<KeyValue> result, int limit)
>           Grab the next row's worth of values with a limit on the number of values to return.
>  
> Method Detail
> next
> boolean next(List<KeyValue> results)
>              throws IOException
>     Grab the next row's worth of values.
>     Parameters:
>         results - return output array 
>     Returns:
>         true if more rows exist after this one, false if scanner is done 
>     Throws:
>         IOException - e
> next
> boolean next(List<KeyValue> result,
>              int limit)
>              throws IOException
>     Grab the next row's worth of values with a limit on the number of values to return.
>     Parameters:
>         result - return output array
>         limit - limit on row count to get 
>     Returns:
>         true if more rows exist after this one, false if scanner is done 
>     Throws:
>         IOException - e

--
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