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-12965) Enhance the delete option to pass Filters
Date Wed, 04 Feb 2015 06:42:36 GMT

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

Anoop Sam John commented on HBASE-12965:

BulkDeleteEndPoint is added for such use case. Here there is no need to fetch rows back to
client and find out RKs from that and issue deletes again. The EP runs at server side avoiding
too many RPCs and data flow btw server and client.  I agree that it might be bit challenging
for users to write code to invoke this EP.  (Any EP).  So what we can do, IMO, is to add some
thing like a Client service class which will take the head ache of calling this EP.
Just like we have AggregationEP and AggregationClient.

What do you think?

> Enhance the delete option to pass Filters
> -----------------------------------------
>                 Key: HBASE-12965
>                 URL: https://issues.apache.org/jira/browse/HBASE-12965
>             Project: HBase
>          Issue Type: Improvement
>          Components: API, Deletes, Filters
>    Affects Versions: 0.98.10
>            Reporter: IMRANKHAN SHAJAHAN
> Scan having the option to pass FIlters and filter the rows based on the filter.
> But for deleting rows, there is no easy way to pass the filters to Delete Object.
> We can do that using below three approach
> 1) Scan the records and create list of Delete object and do the delete. This needs iteration
in client side.
> 2) Writing map reduce
> 3) BulkDeleteEndPoint
> If we implement the option of passing filters in Delete Object, then we dont need to
worry about option 2 and 3.

This message was sent by Atlassian JIRA

View raw message