Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 32279 invoked from network); 31 Jan 2011 04:33:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Jan 2011 04:33:45 -0000 Received: (qmail 51458 invoked by uid 500); 31 Jan 2011 04:33:44 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 51037 invoked by uid 500); 31 Jan 2011 04:33:42 -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 51029 invoked by uid 99); 31 Jan 2011 04:33:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Jan 2011 04:33:41 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jim.pxie@gmail.com designates 209.85.214.41 as permitted sender) Received: from [209.85.214.41] (HELO mail-bw0-f41.google.com) (209.85.214.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Jan 2011 04:33:34 +0000 Received: by bwz16 with SMTP id 16so5401178bwz.14 for ; Sun, 30 Jan 2011 20:33:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=ksnCB05uS3efpRR+yPuvENof4/+bYNrbuPuhD/jwK4g=; b=xXaQvi/gvBvAimBQ+xGVBC9WhD6ALf4PC/YRaFXemILTBvk120zR0qCXwQffXa8KCv s+Hw69lSiFbGJMiMaueOxz1xlTDFCdYgB0f1Rw7I7RNK/7DOEKDokLwgr7Hmoe9oqknw WwExgAux86CbdTitY9yu49MOzSoeSgZtk+VVo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=ZlI5CITbb/BMYcKJrDSxdvSEvatlDa8b6H/IXRzblMIpYfX4+gih8NA4vx90muvEoh nMT26Yzt3ZkwJSqve5efQcfj/eNSyhoBIKtqslLHTFo4/rojSHADustdB1fCdxJFaLSZ dxP52EIUeiypQn+Us5X9NUtvF2t06r64Is42Q= MIME-Version: 1.0 Received: by 10.204.67.204 with SMTP id s12mr4883535bki.196.1296448392962; Sun, 30 Jan 2011 20:33:12 -0800 (PST) Received: by 10.204.45.157 with HTTP; Sun, 30 Jan 2011 20:33:12 -0800 (PST) In-Reply-To: References: Date: Sun, 30 Jan 2011 23:33:12 -0500 Message-ID: Subject: Re: How the batch operations are implemented in HBase? From: Jim X To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks. Yes. This is what I want to know. On Sun, Jan 30, 2011 at 11:10 PM, JinChao Wen wr= ote: > see htable.put(List put) > > if you set autoFlush=3Dtrue, or number of puts you add to htable is excee= d the > writeBufferSize of htable. > The puts will be flushed. > > > > 2011/1/31 Jim X > >> Hi, HBase users, >> >> =A0 =A0 JDBC provides batch operation API. I am assigned to convert a >> JDBC batch implementation into HBase. Does HBase provide some APIs >> like PreparedStatement.addBatch() in JDBC? How do I implement HBase >> batch process in one transaction? >> >> >> Jim >> >