[
https://issues.apache.org/jira/browse/HBASE-21945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell closed HBASE-21945.
---------------------------------------
> 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-alpha-1, 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
(v8.20.7#820007)
