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

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

In order to support all types of deletes we need to have the params
cf names which needs to be deleted
qualifier names which needs to be deleted
timestamp im case we need a time based delete
a type - This is needed when it is a delete version request

The scan ideally need not scan all the column which needs to be deleted. If I 
have a condition based delete, what needs to be scanned is the columns 
involving in the condition..

So taking all these in another POJO, i thought it would be better to accept as 
Delete object. In that we have APIs like deleteColumn(s), deleteFamily etc... 
Users also might be very much knowing this. What do u say Lars? The bit weird 
part I am seeing in this is the rowkey which need to be a fake one..
bq.We'd have to make up fake column qualifiers and qualifiers in the future
Sorry didnt get your mean

Thanks for the reviews and comments 
                
> 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

Reply via email to