[
https://issues.apache.org/jira/browse/HBASE-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254329#comment-13254329
]
jirapos...@reviews.apache.org commented on HBASE-2214:
------------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4726/
-----------------------------------------------------------
(Updated 2012-04-15 13:38:31.680141)
Review request for hbase and Ted Yu.
Summary
-------
HBASE-2214 per scan max buffersize.
This addresses bug HBASE-2214.
https://issues.apache.org/jira/browse/HBASE-2214
Diffs
-----
/src/main/java/org/apache/hadoop/hbase/client/Scan.java 1326084
/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java 1326084
/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
1326084
/src/main/java/org/apache/hadoop/hbase/regionserver/RegionScanner.java
1326084
/src/test/java/org/apache/hadoop/hbase/coprocessor/TestCoprocessorInterface.java
1326084
Diff: https://reviews.apache.org/r/4726/diff
Testing
-------
Thanks,
ferdy
> 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.1
>
> 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
