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 284F310578 for ; Wed, 21 Aug 2013 08:08:42 +0000 (UTC) Received: (qmail 55538 invoked by uid 500); 21 Aug 2013 08:08:39 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 55484 invoked by uid 500); 21 Aug 2013 08:08:35 -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 55465 invoked by uid 99); 21 Aug 2013 08:08:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2013 08:08:33 +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 (athena.apache.org: domain of yongyong313@gmail.com designates 209.85.160.52 as permitted sender) Received: from [209.85.160.52] (HELO mail-pb0-f52.google.com) (209.85.160.52) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2013 08:08:28 +0000 Received: by mail-pb0-f52.google.com with SMTP id wz12so119504pbc.25 for ; Wed, 21 Aug 2013 01:08:08 -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=u8IFmSfDDu+E9B3GzmfUM08yoE1+3wQs90kETlLWWuA=; b=NP8Hf0asrSvwUgOIVPqYI+Fo2SSOVj7t6MQvPggmkeXcTFw+sBd/RHNyKBRPpzacfv boAPidvde+zjv1kcIl51hZWwRjJA2lpbLA0gx1GAXbAunuUWENpf4xDxo7R4H+bvkUdO mwen0FhkSXt2NEWmIlhNWitICkweL9b97jhhyPBC6WbGI+ZmmHkDZa6XnWtutZLEUKMv p4dhsoRcCv1RKcw4NJYCaeawfiYkIAnKjsrWHo3N+5dJxjwEkGfdn3UsdY8NqtUfEdP0 cMPhSojhr4JJW0afAeRsz5MPm4WRaAiEZxAPU56SW8lAWxXezDy/YbNmXnHtHgkZ0NoG sL9w== MIME-Version: 1.0 X-Received: by 10.66.253.4 with SMTP id zw4mr8285983pac.119.1377072488312; Wed, 21 Aug 2013 01:08:08 -0700 (PDT) Received: by 10.66.86.168 with HTTP; Wed, 21 Aug 2013 01:08:08 -0700 (PDT) In-Reply-To: References: Date: Wed, 21 Aug 2013 10:08:08 +0200 Message-ID: Subject: Re: Does HBase supports parallel table scan if I use MapReduce From: yonghu To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=047d7b15adc17ef3d304e470ac8b X-Virus-Checked: Checked by ClamAV on apache.org --047d7b15adc17ef3d304e470ac8b Content-Type: text/plain; charset=ISO-8859-1 Thanks. So, to scan the table just using the java program without using MapReduce will heavily decrease the performance. Yong On Tue, Aug 20, 2013 at 6:02 PM, Jeff Kolesky wrote: > The scan will be broken up into multiple map tasks, each of which will run > over a single split of the table (look at TableInputFormat to see how it is > done). The map tasks will run in parallel. > > Jeff > > > On Tue, Aug 20, 2013 at 8:45 AM, yonghu wrote: > > > Hello, > > > > I know if I use default scan api, HBase scans table in a serial manner, > as > > it needs to guarantee the order of the returned tuples. My question is > if I > > use MapReduce to read the HBase table, and directly output the results in > > HDFS, not returned back to client. The HBase scan is still in a serial > > manner or in this situation it can run a parallel scan. > > > > Thanks! > > > > Yong > > > > > > -- > *Jeff Kolesky* > Chief Software Architect > *Opower* > --047d7b15adc17ef3d304e470ac8b--