[
https://issues.apache.org/jira/browse/HBASE-15274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150825#comment-15150825
]
stack commented on HBASE-15274:
-------------------------------
Patch seems fine but does it get you what you need [~y0un5] (as per [~enis])?
Which version of hbase are you using to read the big rows with? In 1.1+, hbase
does chunking up of the row returning it to the client. Internal to the client
though, it assembles a single result unless you ask to read the result
piecemeal.
> ClientSideRegionScanner's reaction to Scan#setBatch is not consistent between
> HBase versions
> --------------------------------------------------------------------------------------------
>
> Key: HBASE-15274
> URL: https://issues.apache.org/jira/browse/HBASE-15274
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.0.3, 1.1.3, 0.98.17
> Reporter: Youngjoon Kim
> Assignee: Youngjoon Kim
> Priority: Minor
> Attachments: HBASE-15274-0.98.patch, HBASE-15274-branch-1.0.patch
>
>
> In 1.1.3, ClientSideRegionScanner calls RegionScannerImpl#next() with single
> argument, so it honors Scan#setBatch(through defaultScannerContext in
> RegionScannerImpl).
> {code}
> // 1.1.3
> public class ClientSideRegionScanner extends AbstractClientScanner {
> ...
> @Override
> public Result next() throws IOException {
> values.clear();
> scanner.nextRaw(values);
> ...
> {code}
>
> \\
> But in 1.0.3 and 0.98.17, ClientSideRegionScanner calls
> RegionScannerImpl#next() with limit=-1, so it ignores Scan#setBatch.
> {code}
> // 1.0.3 and 0.98.17
> public class ClientSideRegionScanner extends AbstractClientScanner {
> ...
> @Override
> public Result next() throws IOException {
> values.clear();
> scanner.nextRaw(values, -1); // pass -1 as limit so that we see the whole
> row.
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
