[
https://issues.apache.org/jira/browse/HBASE-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475963#comment-13475963
]
Lars Hofhansl edited comment on HBASE-6942 at 10/15/12 4:54 AM:
----------------------------------------------------------------
For the V4 patch. You do not need to check all the operationStatus', you can
break out of the loop as soon as you find the first status that is not success.
Can do that on commit. +1 on the rest of the patch.
Edit: Forgot a "not" in the 2nd sentence.
was (Author: lhofhansl):
For the V4 patch. You do need to check all the operationStatus', you can
break out of the loop as soon as you find the first status that is not success.
Can do that on commit. +1 on the rest of the patch.
> Endpoint implementation for bulk delete rows
> --------------------------------------------
>
> Key: HBASE-6942
> URL: https://issues.apache.org/jira/browse/HBASE-6942
> Project: HBase
> Issue Type: Improvement
> Components: Coprocessors, Performance
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Fix For: 0.94.3, 0.96.0
>
> Attachments: HBASE-6942.patch, HBASE-6942_V2.patch,
> HBASE-6942_V3.patch, HBASE-6942_V4.patch
>
>
> We can provide an end point implementation for doing a bulk deletion of
> rows(based on a scan) at the server side. This can reduce the time taken for
> such an operation as right now it need to do a scan to client and issue
> delete(s) using rowkeys.
> Query like delete from table1 where...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
