[
https://issues.apache.org/jira/browse/HBASE-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475911#comment-13475911
]
Lars Hofhansl commented on HBASE-6942:
--------------------------------------
Yeah, passing the delete option as scan attribute is a bit weird. But I can see
this both ways.
It would be nice if all of this could be strictly controlled by the scan we
pass in. The scan would (through the attribute) indicate the delete type to use
and also describe the KVs that are to be deleted.
Also not sure about the template Delete... We'd have to make up fake column
qualifiers and qualifiers in the future... Since this is an advanced feature we
could pass the delete type (from KeyValue), or maybe a new enum to indicate
what we want to do.
So I can see this going both ways. In either case this should probably return
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
