hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17045) Unify the implementation of small scan and regular scan
Date Tue, 08 Nov 2016 05:50:58 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646605#comment-15646605
] 

stack commented on HBASE-17045:
-------------------------------

Appreciate the reminder that just because we did it one way in synchronous Scan implementation
doesn't mean we have to repeat in new async Scan.

> 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, 1.4.0
>            Reporter: Duo Zhang
>             Fix For: 2.0.0
>
>
> 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)

Mime
View raw message