[
https://issues.apache.org/jira/browse/HBASE-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476775#comment-13476775
]
Lars Hofhansl commented on HBASE-6942:
--------------------------------------
Sounds good. Just worried that N will necessarily be (much?) larger than M.
One last thing. Let's not pass things as Scan attributes, it just makes it more
obtuse (IMHO :) ). We can have an API:
{{BulkDeleteResponse delete(Scan scan, DeleteType type, Long timestamp)}}
timestamp could be null (hence a Long). If it is null, we use the lastest
timestamp for ROW/FAMILY/COLUMN and the KV's timestamp for VERSION, otherwise
we can use the passed timestamp... That should account for all use cases.
(Sorry, I think it was my comment to use a Scan only to made you change it...?
That was not what I meant... I just think it's better to be explicit about
extra parameters for an operation).
Does that sound OK?
Documenting this will be tricky. I can have a shot at that (if you like, Anoop.
If you prefer to do that, that's fine too).
Thanks for all the work on this and the patience, this is an awesome feature!
Eventually, since we made it so general now, I *can* see this as an official
API in HTable... But let's do that in an another jira (if others agree).
> 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
