Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 16 Oct 2012 05:39:04 +0000 (UTC)
From: "Anoop Sam John (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <377454688.49964.1350365944337.JavaMail.jiratomcat@arcas>
In-Reply-To: <125266612.163883.1349326627533.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-6942) Endpoint implementation for bulk
 delete rows
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Lars, I think other than the version type the patch is in line with your thinking. With Version type the main difference is patch V5 considers deleting only one version of a column where as in your comment it is N version depending on the scan (how many KVs it returned).. Yes I agree 100% with you on this

wrt FAMILY delete type, I think we can handle. Let the scan returns N KVs for a row. If that N KVs corresponds to M families, we delete all M families. Also TS can be used here as well...
What do u say Lars?
Thanks

                
> 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