[
https://issues.apache.org/jira/browse/HBASE-17595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937940#comment-15937940
]
Hadoop QA commented on HBASE-17595:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s
{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 7s {color}
| {color:red} HBASE-17595 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.3.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12860098/HBASE-17595-addendum-branch-1.patch
|
| JIRA Issue | HBASE-17595 |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/6205/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> 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-addendum-branch-1.patch,
> HBASE-17595-addendum.patch, HBASE-17595-addendum-v1.patch,
> HBASE-17595-addendum-v2.patch, HBASE-17595-addendum-v3.patch,
> 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)
