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 Tue, 16 Oct 2012 04:13:03 GMT

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

Anoop Sam John commented on HBASE-6942:
---------------------------------------

bq.In patch v5, rowBatchSize isn't used in the following call:
bq.hasMore = scanner.next(results);

Ted this code part is same in older versions also. We use the rowBatchSize to accumulate the
rows so that all can be deleted as one unit. This is not scan batch.. We do rowBatchSize times
scanner.next(results) just like HRS

bq.In createDeleteMutation(), List<KeyValue> is passed and row key is retrieved from
the first KeyValue.Is this intended ?
Yes. All the KVs in this list will be part of same row.. So we can use any of the KV to get
the rowkey. All rowkeys will be same..
                
> 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

Mime
View raw message