You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Youngjoon Kim (JIRA)" <ji...@apache.org> on 2016/02/17 02:05:18 UTC
[jira] [Updated] (HBASE-15274) ClientSideRegionScanner's reaction
to Scan#setBatch is not consistent between HBase versions
[ https://issues.apache.org/jira/browse/HBASE-15274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Youngjoon Kim updated HBASE-15274:
----------------------------------
Attachment: HBASE-15274-0.98.patch
HBASE-15274-branch-1.0.patch
Upload patches for branch-1.0 and 0.98, which fix ClientSideRegionScanner to honor Scan#setBatch.
> 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)