hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17595) Add partial result support for small/limited scan
Date Mon, 13 Mar 2017 01:25:04 GMT

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

Duo Zhang commented on HBASE-17595:
-----------------------------------

I've done some experiment and found a suitable way to fix the problem, both server side and
client side. But for client side, as HBASE-15484 added more logics for handling partial results,
it is a bit awkward that we need to implement the same logic for both sync client and async
client but with different ways. So I plan to address HBASE-17740 first, and refactor the sync
client to also use ScanResultCache to deal with partial results. And then back to this issue.

Thanks.

> Add partial result support for small/limited scan
> -------------------------------------------------
>
>                 Key: HBASE-17595
>                 URL: https://issues.apache.org/jira/browse/HBASE-17595
>             Project: HBase
>          Issue Type: Sub-task
>          Components: asyncclient, Client, scan
>    Affects Versions: 2.0.0, 1.4.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Critical
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-17595-branch-1.patch, HBASE-17595.patch, HBASE-17595-v1.patch
>
>
> The partial result support is marked as a 'TODO' when implementing HBASE-17045. And when
implementing HBASE-17508, we found that if we make small scan share the same logic with general
scan, the scan request other than open scanner will not have the small flag so the server
may return  partial result to the client and cause some strange behavior. It is solved by
modifying the logic at server side, but this means the 1.4.x client is not safe to contact
with earlier 1.x server. So we'd better address the problem at client side. Marked as blocker
as this issue should be finished before any 2.x and 1.4.x releases.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message