[
https://issues.apache.org/jira/browse/HBASE-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475839#comment-13475839
]
Anoop Sam John commented on HBASE-6942:
---------------------------------------
Regarding passing the rowBatchSize in attributes of Scan, I am in half mind
Ted.. As this attribute is related with the delete op and not Scan...
Requesting your opinion also Lars..
I was thinking of enhancing this for doing all kind of deletes. We have CF
delete, column delete, version delete and time based KVs delete etc... Ideally
better we can support all these kind of deletes. What is in my mind is to
accept a Delete object as a template in this Endpoint... Well for Delete we
need some byte[] as rowkey.. Any dummy(empty byte[]) is okey.. What we need is
to follow that Delete object create Delete objects in Endpoint. Thougts??
Yes Ted in that case we can pass back the number of KVs deleted..
> 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
