hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6942) Endpoint implementation for bulk delete rows
Date Tue, 16 Oct 2012 04:35:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476728#comment-13476728

Lars Hofhansl commented on HBASE-6942:

I also think we have different use cases in mind. Passing the timestamp for a version delete
through the Scan is not useful (I think) rather the timestamps should be taken from the scanned

I think you misunderstood what I was saying with "it should be controlled by the scan". What
I meant was: Via the scan we will select a bunch of KeyValues. Then these KeyValues indicate
what would be deleted (together with the various delete types).

I.e. a user can pass the VERSION delete type along with a scan selecting a bunch of KeyValue.
Then these exact KeyValues will be deleted.
Likewise when COLUMN is passed the passed scan will identify a bunch of KeyValues to identify
the columns to be delete (caller should make sure - only for performance - that the same column
KeyValue does not occur multiple times)
Same for Families and Rows.

So we only pass a scan (with NO extra attributes in the scan) along with an indicator if the
delete type. That should be enough.

> 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,
> 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

View raw message