Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 41891 invoked from network); 17 Jul 2009 05:48:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Jul 2009 05:48:25 -0000 Received: (qmail 27629 invoked by uid 500); 17 Jul 2009 05:49:30 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 27585 invoked by uid 500); 17 Jul 2009 05:49:30 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 27575 invoked by uid 99); 17 Jul 2009 05:49:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jul 2009 05:49:30 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jul 2009 05:49:21 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1MRgJY-0003Vi-UR for hbase-user@hadoop.apache.org; Thu, 16 Jul 2009 22:49:00 -0700 Message-ID: <24528949.post@talk.nabble.com> Date: Thu, 16 Jul 2009 22:49:00 -0700 (PDT) From: Peter Rietzler To: hbase-user@hadoop.apache.org Subject: Batched Gets and Deletes by Id / Performance Issues ? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: peter.rietzler@smarter-ecommerce.com X-Virus-Checked: Checked by ClamAV on apache.org Hi First of all thanks for your great work! We are enjoying using HBase in our project :) One of our HBase tables uses UUIDs for keys. The character of the data is random access and we are indexing the rows with an external indexer. The access characteristic is much like you would do with a traditional SQL statement - Issue a query to the index and then get all associated rows using the list of returned ids (typically from a few 100 up to around 100.000 rows ...). The same applies for deletion. While batch updating is available I miss an opportunity to batch fetch and batch delete rows by id. I currently use HTable.getRow() and HTable.deleteAll() for these operations - however - both of the operations perform pretty poor for more than a couple of 100 rows (I guess it's because an IPC call needs to be send for each call...). Unfortunately scanning is not an issue for this use case. Is it planned to provide batch random access batch fetches ? Something like HTable.getRows(list of ids) and HTable.deleteAll(list of ids) would be perfect :) Cheers, Peter -- View this message in context: http://www.nabble.com/Batched-Gets-and-Deletes-by-Id---Performance-Issues---tp24528949p24528949.html Sent from the HBase User mailing list archive at Nabble.com.