[
https://issues.apache.org/jira/browse/HBASE-17045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15819499#comment-15819499
]
Duo Zhang edited comment on HBASE-17045 at 1/12/17 2:59 PM:
------------------------------------------------------------
We already have a moreResultsInRegion flag that indicates if we have finished
scanning a region, if it is false then we do not need to call close.
And yeah I have not change the sync client yet. Also the inclusive/exclusive of
startRow/endRow change. It is not straight forward as we have replica read
support for sync client and cause the calling trace very complicated. Will open
new issues to implement them for sync client and backport to branch-1.
Thanks.
was (Author: apache9):
We already have a moreResultsInRegion flag that indicates if we have finished
scanning a region, if it is false then we do not need to call close.
And yeah I have not change the sync client yet. Also the inclusive/exclusive of
startRow/endRow change. It is not strange forward as we have replica read
support for sync client and cause the calling trace very complicated. Will open
new issues to implement them for sync client and backport to branch-1.
Thanks.
> 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-v1.patch, HBASE-17045-v2.patch,
> HBASE-17045.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)
