[
https://issues.apache.org/jira/browse/HBASE-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477919#comment-13477919
]
Anoop Sam John commented on HBASE-6942:
---------------------------------------
HBASE-6942_DeleteTemplate patch with Delete template approach
Here one thing we can not directly implement is the deletion of N versions..
With scan based approach as every thing governed by the scan result it is easy
With both these I feel being a user go with Scan based approach will be easy.
The mixed kind of delete only will be not possible in that case
Requesting opinion from others
> 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_DeleteTemplate.patch, HBASE-6942.patch,
> HBASE-6942_V2.patch, HBASE-6942_V3.patch, HBASE-6942_V4.patch,
> HBASE-6942_V5.patch, HBASE-6942_V6.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
