[
https://issues.apache.org/jira/browse/HBASE-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferdy Galema updated HBASE-2214:
--------------------------------
Assignee: Ferdy Galema
As mentioned in HBASE-5607, I will pick up this issue.
First of all:
I looked at the patch and I noticed that is huge. A lot of unnecessary changes
are in it, whitespace/reformatting and such. It is very difficult to work with
this when applying it with regular svn patch tools. Therefore, if you don't
mind, I want to start over from scratch. (Of course it has been a while so a
lot of changes won't apply anyway).
Secondly, does this feature replaces the old number of rows caching? I like to
propose that it is additional. So: A user specifying 100 rows and 10MB for a
Scan will get chunks that are either capped at 100 rows, or 10MB, whichever
limit comes first. Do you agree?
> 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
> Labels: noob
> Fix For: 0.96.0
>
> Attachments: 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
