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 CCF4110818 for ; Thu, 11 Apr 2013 00:33:31 +0000 (UTC) Received: (qmail 66847 invoked by uid 500); 11 Apr 2013 00:33:29 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 66794 invoked by uid 500); 11 Apr 2013 00:33:29 -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 66786 invoked by uid 99); 11 Apr 2013 00:33:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Apr 2013 00:33:29 +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 saint.ack@gmail.com designates 209.85.214.50 as permitted sender) Received: from [209.85.214.50] (HELO mail-bk0-f50.google.com) (209.85.214.50) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Apr 2013 00:33:23 +0000 Received: by mail-bk0-f50.google.com with SMTP id jg1so529571bkc.37 for ; Wed, 10 Apr 2013 17:33:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Z7OJy1Zp00dcLubUHbHPpTjjlVjCfwEpqXVjUhElRPY=; b=cOgKa4qOFXY+tpbeCgivfBZ6i1EeAVWFEMuaDuZdS/zEc+sNI342yJCeLUr2bGlrtf YTYdLVfMJWXF/h/gPEWshHNhavxA7/v+ROHjqAz2Pd7NBLp5WUm6sV8QQt6N7MJ+E2jA A94G5/IzMTtx12bm9/NZP9fF8ZKySw5+aGjaeYqhtqCEtNx98TWEZQAfh5S3YqNSGC6W w+c2j2BunvBfWO0JzdDN+60yhlPP0d5knJytIbw073xzcDEI5zc70s5Hb1k1LJeEn5xy 9ucor60UnNo11Jy1AR379qp8vL5MoCTV8/3fZ6zTR3WKdqLwXwF+NJ2C0LMUpHBc+tU5 ltgw== MIME-Version: 1.0 X-Received: by 10.205.71.6 with SMTP id yi6mr1652517bkb.8.1365640383248; Wed, 10 Apr 2013 17:33:03 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.204.147.22 with HTTP; Wed, 10 Apr 2013 17:33:03 -0700 (PDT) In-Reply-To: References: Date: Wed, 10 Apr 2013 17:33:03 -0700 X-Google-Sender-Auth: 5paX5zYU36rAVjTNoLEOCtkndas Message-ID: Subject: Re: MapReduce: Reducers partitions. From: Stack To: Hbase-User Content-Type: multipart/alternative; boundary=f46d040f9dc8ef6b8b04da0aed59 X-Virus-Checked: Checked by ClamAV on apache.org --f46d040f9dc8ef6b8b04da0aed59 Content-Type: text/plain; charset=UTF-8 On Wed, Apr 10, 2013 at 12:01 PM, Jean-Marc Spaggiari < jean-marc@spaggiari.org> wrote: > Hi Greame, > > No. The reducer will simply write on the table the same way you are doing a > regular Put. If a split is required because of the size, then the region > will be split, but at the end, there will not necessary be any region > split. > > In the usecase described below, all the 600 lines will "simply" go into the > only region in the table and no split will occur. > > The goal is to partition the data for the reducer only. Not in the table. > Then just use the default partitioner? The suggestion that you use HTablePartitioner seems inappropriate to your task. See the sink doc here: http://hadoop.apache.org/docs/r2.0.3-alpha/api/org/apache/hadoop/mapreduce/lib/partition/HashPartitioner.html St.Ack --f46d040f9dc8ef6b8b04da0aed59--