Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 26 Jul 2012 19:50:35 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <933220833.107645.1343332235435.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HBASE-2214) Do HBASE-1996 -- setting size to
 return in scan rather than count of rows -- properly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lars Hofhansl commented on HBASE-2214:
--------------------------------------

@Ferdy, are you sure you do not want to work on this anymore?
I'll change Scan.java to be able to deal with two different version, so we can get this in 0.94 (admittedly, that is a small change only).

bq. Maybe the ClientScanner could modify the Scan that it passes the max scanner result it uses to the region server

Of course the requires the server to actually trust the client. Although I think with a rogue client it is quite easy to kill/mess-with a RegionServer in many other areas.
                
> Do HBASE-1996 -- setting size to return in scan rather than count of rows -- properly
> -------------------------------------------------------------------------------------
>
>                 Key: HBASE-2214
>                 URL: https://issues.apache.org/jira/browse/HBASE-2214
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: stack
>             Fix For: 0.96.0, 0.94.2
>
>         Attachments: HBASE-2214-0.94-v2.txt, HBASE-2214-0.94-v3.txt, HBASE-2214-0.94.txt, HBASE-2214-v4.txt, HBASE-2214-v5.txt, HBASE-2214-v6.txt, HBASE-2214-v7.txt, HBASE-2214_with_broken_TestShell.txt
>
>
> The notion that you set size rather than row count specifying how many rows a scanner should return in each cycle was raised over in hbase-1966.  Its a good one making hbase "regular" though the data under it may vary.  HBase-1966 was committed but the patch was constrained by the fact that it needed to not change RPC interface.  This issue is about doing hbase-1966 for 0.21 in a clean, unconstrained way.

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