Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BC2B210802 for ; Thu, 26 Sep 2013 16:09:57 +0000 (UTC) Received: (qmail 76547 invoked by uid 500); 26 Sep 2013 16:09:57 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 76465 invoked by uid 500); 26 Sep 2013 16:09:55 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 76411 invoked by uid 99); 26 Sep 2013 16:09:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Sep 2013 16:09:51 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.215.50 as permitted sender) Received: from [209.85.215.50] (HELO mail-la0-f50.google.com) (209.85.215.50) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Sep 2013 16:09:46 +0000 Received: by mail-la0-f50.google.com with SMTP id gx14so1153317lab.37 for ; Thu, 26 Sep 2013 09:09:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=xqADOpPSGoJoDm1bHqbjoyFcDn0dMgrl77/Tn6D7sT0=; b=vsWfYwqbkn9cycOqFx+WM0h5zabXHz4ahEYAX9GzABnwsHzyHo2gBWEBx5f7eKmvX4 +iK5ykJqP3mDxNvGC/9u7C+tKRuDqLCf3heWm2D+IscqqBEYbdF4QaN+ZALyUBv5FH2r I0GaZ4CvCbCjLblcuhK+xnoW+0wAgEASpQ6xs2nmcORiXtzm5ZRGzOcigL7s9x0Wuvd4 KTVlUzqygy4mTSTOwUmF5GeXQdmxc7IeB8TDxU7XCeN/ytsw/EJHl49H9EXrmbooQnHg NK8sEyfKFhCWAzhwDq/Yn2rgKTDwzdMhKlOYe/Aov01Njc96aD6bnfofKqg6KfKF4CtH x7vA== MIME-Version: 1.0 X-Received: by 10.152.115.176 with SMTP id jp16mr1248109lab.17.1380211765546; Thu, 26 Sep 2013 09:09:25 -0700 (PDT) Received: by 10.112.129.40 with HTTP; Thu, 26 Sep 2013 09:09:25 -0700 (PDT) In-Reply-To: References: Date: Thu, 26 Sep 2013 09:09:25 -0700 Message-ID: Subject: Re: What will be the exact format of the object array returned by HTable batch function ? From: Ted Yu To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a11c3509600148004e74b9876 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3509600148004e74b9876 Content-Type: text/plain; charset=ISO-8859-1 You can take a look at HConnectionManager#processBatchCallback(), starting line 1672 (0.94 branch): // step 1: break up into regionserver-sized chunks and build the data structs Action action = new Action(row, i); Each Action has the original index to the List of Row's. This would be used when filling results array. Cheers On Thu, Sep 26, 2013 at 8:20 AM, Maxime wrote: > Hi, > > I would like to use the HTable batch function to regroup multiple Increment > operations. But I am not sure of the format that is returned by this > function. > > Please, could someone tell me if the returned array will keep the order of > the List of Row provided to the batch function ? > If the result of the first Row can be accessed in result[0] (and will be > the > new value post increment), second Row in result[1] etc.. ? > > Thanks, > Maxime > > --001a11c3509600148004e74b9876--