[
https://issues.apache.org/jira/browse/HBASE-17045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833509#comment-15833509
]
Duo Zhang commented on HBASE-17045:
-----------------------------------
Ready for review sir. [~stack] [~enis].
> Unify the implementation of small scan and regular scan
> -------------------------------------------------------
>
> Key: HBASE-17045
> URL: https://issues.apache.org/jira/browse/HBASE-17045
> Project: HBase
> Issue Type: Sub-task
> Components: Client, scan
> Affects Versions: 2.0.0
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Fix For: 2.0.0
>
> Attachments: HBASE-17045.patch, HBASE-17045-v1.patch,
> HBASE-17045-v2.patch, HBASE-17045-v3.patch, HBASE-17045-v4.patch,
> HBASE-17045-v5.patch, HBASE-17045-v7.patch, HBASE-17405-v6.patch
>
>
> See [~enis]'s comment in HBASE-16838
> https://issues.apache.org/jira/browse/HBASE-16838?focusedCommentId=15637803&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15637803
> But there is another scenario that we need small scan is that, we do not know
> the stop row but we only want a small set of results. For example, in the
> implementation of region locator, we will use small scan and set caching to 1
> as we only need one row.
> So I think we need to add a new option(maybe called limit?) for the scan
> object, and deprecate the small option. And the server side modification
> should also be committed to branch-1 to simplify the logic of async client in
> 2.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
