[
https://issues.apache.org/jira/browse/HBASE-21945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16776338#comment-16776338
]
Hudson commented on HBASE-21945:
--------------------------------
Results for branch branch-2.2
[build #64 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/64/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/64//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/64//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/64//JDK8_Nightly_Build_Report_(Hadoop3)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/64//console].
> Maintain the original order when sending batch request
> ------------------------------------------------------
>
> Key: HBASE-21945
> URL: https://issues.apache.org/jira/browse/HBASE-21945
> Project: HBase
> Issue Type: Sub-task
> Components: asyncclient, Client
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.3.0.
>
> Attachments: HBASE-21945.patch, HBASE-21945.patch, HBASE-21945.patch
>
>
> Find this when implementing HBASE-21717. In some UT we put several good
> requests and bad requests together, and expect only the bad ones to fail.
> This usually depends on the grouping at rs side, if we group the good one and
> the bad one together as a batch, it will fail them all. So usually in test we
> will insert an increment or append in the middle to break them into two
> groups when executing at RS side.
> So if we do not maintain the order, at the rs side, the increment or append
> may comes first or last, then the good ones and bad ones will be grouped and
> cause all of them to fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
