You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2016/12/19 01:42:58 UTC

[jira] [Commented] (HBASE-17320) Add inclusive/exclusive support for startRow and endRow of scan

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

Duo Zhang commented on HBASE-17320:
-----------------------------------

Not easy as I think before. One problem is that, for reversed scan, we do not handle LastOnRowCell so seekScanners can not seek to the next(previous actually) row of the given LastOnRowCell. Although I think I can fix this, there are other big problems in the client code. First is that we need to reset the inclusive of startRow at a proper place as we will reset the startRow for different scan request but we only want to exclude the startRow of the first request. And we also need to change the locating region related code as the row before or after the give row may not be in the same region.

So I prefer to set this to 2.0 only first to add the support in async table as I'm more familiar with the code of async table. Will add the support for the old implementation and backport it to branch-1 if I have time.

Thanks.

> Add inclusive/exclusive support for startRow and endRow of scan
> ---------------------------------------------------------------
>
>                 Key: HBASE-17320
>                 URL: https://issues.apache.org/jira/browse/HBASE-17320
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client, scan
>    Affects Versions: 2.0.0, 1.4.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>             Fix For: 2.0.0, 1.4.0
>
>
> This is especially useful when doing reverse scan. HBASE-17168 maybe a more powerful solution but we need to be careful about the atomicity, and I do not think we will provide the feature to end user. But I think it is OK to provide inclusive/exclusive option to end user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)