[
https://issues.apache.org/jira/browse/HBASE-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475536#comment-13475536
]
Lars Hofhansl commented on HBASE-6942:
--------------------------------------
I think Ted is right, looking at FirstKeyOnlyFilter, it can be combined with
other filters into FilterList with Operator.MUST_PASS_ALL.
If we always combine with the FirstKeyOnlyFilter we can keep using a List for
the deletedRowKeys, because there's only one ever.
Sorry for the length of the discussion here, Anoop. Almost there :)
+1 for the rest of the patch. (Have you tried it in production?)
And +1 for dealing with other delete types in a separate jira... Would be nice
to use the same method, though, and just pass in an extra flag to indicate with
type of delete to use (and hence how to filter the results).
> 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
>
>
> 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
