[
https://issues.apache.org/jira/browse/HBASE-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475748#comment-13475748
]
Ted Yu commented on HBASE-6942:
-------------------------------
When FirstKeyOnlyFilter is not involved, this endpoint has the potential to
delete selected KeyValue's.
{code}
+public class BulkDeleteResponse implements Serializable {
+ private static final long serialVersionUID = -8192337710525997237L;
+ private Long rowsDeleted;
+ private IOException ioException;
{code}
Do you think the above response should have a field which notes the number of
KeyValue's deleted ?
When this feature is made available to public, people would start using it.
It would be nice for API to accommodate future enhancement without requiring
users to change the clients.
Nice job, Anoop.
> 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
