[jira] [Comment Edited] (HBASE-6942) Endpoint implementation for bulk delete rows

["Ted Yu (JIRA)" <ji...@apache.org>]

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

Ted Yu edited comment on HBASE-6942 at 10/13/12 4:24 PM:
---------------------------------------------------------

Looks like FilterList.filterKeyValue() should be enhanced (with a new setting, in another JIRA) where ReturnCode.NEXT_ROW would be returned for the second occurrence of the same row key whose first ReturnCode was ReturnCode.INCLUDE.
                
      was (Author: yuzhihong@gmail.com):
    Looks like FilterList.filterKeyValue() should be enhanced (in another JIRA) where ReturnCode.NEXT_ROW would be returned for the second occurrence of the same row key whose first ReturnCode was ReturnCode.INCLUDE.
                  
> 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