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 36FF311253 for ; Fri, 27 Jun 2014 07:22:54 +0000 (UTC) Received: (qmail 16301 invoked by uid 500); 27 Jun 2014 07:22:52 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 16228 invoked by uid 500); 27 Jun 2014 07:22:52 -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 16215 invoked by uid 99); 27 Jun 2014 07:22:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2014 07:22:51 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of konstt2000@gmail.com designates 209.85.212.181 as permitted sender) Received: from [209.85.212.181] (HELO mail-wi0-f181.google.com) (209.85.212.181) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jun 2014 07:22:49 +0000 Received: by mail-wi0-f181.google.com with SMTP id n3so2296061wiv.14 for ; Fri, 27 Jun 2014 00:22: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=quaYy6Kx30JNdEd61psoO8XqWnExdishf/9SjkqrExM=; b=dPYfFW0/rcITrrfHSLNzWdDYRIWDHi5sLUuIZYia+/kc+wiunoiMAU/4dFLnX+95k/ x73F9TMTK7NmKaKvnqyfkydqBbg9MqTh7y3b6IkXKSFtW5G+JKER2vBsyqO3gxOGCydC D5zO2v8yczceBwEt3o46qgO3rcpoaALCiVc7eJbBnnkrapHf6wKwgGkf+WPV1McQ9Af3 aiqktzH1kLhovLUyb5rWmXGRddu0pWv84wCzw/NCmpMX4gr3ZtZGurL9gzkXFNx9OXMi 9tCRM9UqAsOnsZMDp9vfSYLVJf349kirHW3LU3RFuu+E9JeMXQnXgKTtOaPVglmt6kqi iKfQ== MIME-Version: 1.0 X-Received: by 10.194.142.148 with SMTP id rw20mr22914256wjb.69.1403853745567; Fri, 27 Jun 2014 00:22:25 -0700 (PDT) Received: by 10.217.54.130 with HTTP; Fri, 27 Jun 2014 00:22:25 -0700 (PDT) In-Reply-To: References: Date: Fri, 27 Jun 2014 09:22:25 +0200 Message-ID: Subject: Re: Store data in HBase with a MapReduce. From: Guillermo Ortiz To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=089e013a27c4d23af004fccc2b40 X-Virus-Checked: Checked by ClamAV on apache.org --089e013a27c4d23af004fccc2b40 Content-Type: text/plain; charset=UTF-8 If I have to.... how me reducers I should have?? as many as number of regions?? I have read about HRegionPartitioner, but it has some limitations, and you have to be sure that any region isn't going to split while you're putting new data in your table. Is it only for performance? what could it happen if you put too many data in your table and it splits an region with a HRegionPartitioner? 2014-06-26 21:43 GMT+02:00 Stack : > Be sure to read http://hbase.apache.org/book.html#d3314e5975 Guillermo if > you have not already. Avoid reduce phase if you can. > > St.Ack > > > On Thu, Jun 26, 2014 at 8:24 AM, Guillermo Ortiz > wrote: > > > I have a question. > > I want to execute an MapReduce and the output of my reduce it's going to > > store in HBase. > > > > So, it's a MapReduce with an output which it's going to be stored in > HBase. > > I can do a Map and use HFileOutputFormat.configureIncrementalLoad(pJob, > > table); but, I don't know how I could do it if I have a Reduce as well,, > > since the configureIncrementalLoad generates an reduce. > > > --089e013a27c4d23af004fccc2b40--