[
https://issues.apache.org/jira/browse/HBASE-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475542#comment-13475542
]
Anoop Sam John commented on HBASE-6942:
---------------------------------------
bq.Please add annotation for audience and stability.
This is to be there with Trunk only right? In 0.94 I think we should not add as
per the Hadoop support
bq.Should a Set be used ? The use case is for deleting entire rows. We just
need to collect unique row keys.
May be List is fine. Will be an issue when batching is there. But not
expecting.. Any way Set seems perfect. I will change.
FirstKeyOnlyFilter - Let me test one thing.. Having one doubt...
bq.Sorry for the length of the discussion here, Anoop. Almost there
No problems at all Lars.. :)
bq.Would be nice to use the same method, though, and just pass in an extra flag
to indicate with type of delete to use
Yes this is what in mind too...
> 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
