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

Ferdy Galema updated HBASE-2214:
--------------------------------

    Fix Version/s:     (was: 0.96.0)
                   0.94.0
           Labels:   (was: noob)
           Status: Patch Available  (was: In Progress)

This is my first attempt. It is not finished, I was just curious if this is the 
right way to go. Note that it has no tests, because I was not sure where to 
include those. This patch piggybacks on the existing functionality introduced 
in HBASE-1996. (It seems that this also has no tests.)

I tried to add a test to TestHRegion and TestScanner, but it seems the existing 
tests bypass the HRegionServer "Result[] next(final long scannerId, int 
nbRows)" method.

                
> 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
>            Assignee: Ferdy Galema
>             Fix For: 0.94.0
>
>         Attachments: HBASE-2214-0.94.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

        

Reply via email to