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

Dave Latham updated HBASE-2214:
-------------------------------

    Description: 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-1996.  Its a good one making hbase "regular" though the data under it may 
vary.  HBASE-1996 was committed but the patch was constrained by the fact that 
it needed to not change RPC interface.  This issue is about doing HBASE-1996 
for 0.21 in a clean, unconstrained way.  (was: 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-1996 was committed but the patch was 
constrained by the fact that it needed to not change RPC interface.  This issue 
is about doing HBASE-1996 for 0.21 in a clean, unconstrained way.)

> 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.95.0
>
>         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-1996.  Its a 
> good one making hbase "regular" though the data under it may vary.  
> HBASE-1996 was committed but the patch was constrained by the fact that it 
> needed to not change RPC interface.  This issue is about doing HBASE-1996 for 
> 0.21 in a clean, unconstrained way.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to