[ https://issues.apache.org/jira/browse/HBASE-6942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476126#comment-13476126 ]
Anoop Sam John commented on HBASE-6942: --------------------------------------- Some drawbacks due to not taking Delete object 1. When it is a timestamp based delete same TS to be used for all the columns where as in normal delete diff TS can be used 2. Types can not be mixed. In normal delete one CF delete and other one's column delete and yet others version delete can be combined Just mentioning the differences. Dont think these are common usecases. So I am fine with the current way of ours. Requesting thoughts from other users who having similar usecases. > 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