[ https://issues.apache.org/jira/browse/HBASE-15274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148765#comment-15148765 ]
Youngjoon Kim commented on HBASE-15274: --------------------------------------- Yes, I'll try this. I think 1.1.3 is correct, so I'll make patches targeting branch 0.98 and branch-1.0, is it OK? > 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 > Priority: Minor > > 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)