hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6942) Endpoint implementation for bulk delete rows
Date Sat, 13 Oct 2012 03:39:03 GMT

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

Anoop Sam John commented on HBASE-6942:

Yes Lars I am adding the logic to count the rows deleted as this way.. But I was not able
to test this.. Because getting a Status code of FAILURE or SANITY_FAILURE seems not possible
in this case...  Any way better the code be in correct shape... This is the apt way to know...

Regarding Jerry's comment - His use case seems different than ours.. Ours is a range based
row deletes.. Not even condition based. But I expect some one can have condition based delete
also.. Any way we give Scan so it is possible.. I am specifically mentioning that this is
used for deleting the entire row... 

We can have separate jira issues to deal with CF deletes, column deletes, version deletes
etc... agree Lars? I will be happy to work with that.. Also will give a trunk version once
94 based version is fine for commit.

This delete performance is being discussed in different user mail threads I guess.. SO this
kind of a example Endpoint impl will help folks...
> 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
> 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