[
https://issues.apache.org/jira/browse/HBASE-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476292#comment-13476292
]
Ted Yu commented on HBASE-6942:
-------------------------------
An alternative, assuming Delete is passed as a parameter to BulkDeleteEndpoint,
would be to reduce DeleteType to two enum values: ROW and NON_ROW.
For NON_ROW case, the user is able to specify any combination of deletions
based on non-null row key (just a placeholder):
{code}
Delete del = new Delete(row);
del.deleteFamily(FAMILY1);
{code}
In createDeleteMutation(), we call Delete.getFamilyMap() and plug in the row
key obtained from the scanning for all KeyValue's contained in family map.
> 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, HBASE-6942_V5.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
