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 718FD10813 for ; Wed, 29 Jan 2014 20:53:22 +0000 (UTC) Received: (qmail 28127 invoked by uid 500); 29 Jan 2014 20:53:19 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 28032 invoked by uid 500); 29 Jan 2014 20:53:18 -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 28024 invoked by uid 99); 29 Jan 2014 20:53:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jan 2014 20:53:18 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of wtan@us.ibm.com designates 32.97.182.139 as permitted sender) Received: from [32.97.182.139] (HELO e9.ny.us.ibm.com) (32.97.182.139) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jan 2014 20:53:09 +0000 Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 29 Jan 2014 15:52:48 -0500 Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Wed, 29 Jan 2014 15:52:45 -0500 Received: from b01cxnp22033.gho.pok.ibm.com (b01cxnp22033.gho.pok.ibm.com [9.57.198.23]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id ABE7F38C8045 for ; Wed, 29 Jan 2014 15:52:44 -0500 (EST) Received: from d01av05.pok.ibm.com (d01av05.pok.ibm.com [9.56.224.195]) by b01cxnp22033.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s0TKqi9B9109966 for ; Wed, 29 Jan 2014 20:52:44 GMT Received: from d01av05.pok.ibm.com (localhost [127.0.0.1]) by d01av05.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s0TKqiXf028278 for ; Wed, 29 Jan 2014 15:52:44 -0500 Received: from d01ml605.pok.ibm.com (d01ml605.pok.ibm.com [9.63.8.148]) by d01av05.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s0TKqi6V028275 for ; Wed, 29 Jan 2014 15:52:44 -0500 In-Reply-To: <1391028493.66723.YahooMailNeo@web140606.mail.bf1.yahoo.com> References: <1391028493.66723.YahooMailNeo@web140606.mail.bf1.yahoo.com> To: user@hbase.apache.org MIME-Version: 1.0 Subject: Re: larger HFile block size for very wide row? X-KeepSent: 106B9F34:D1BDBCCF-85257C6F:00727BDE; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.5.3FP4 SHF39 May 13, 2013 Message-ID: From: Wei Tan Date: Wed, 29 Jan 2014 15:52:43 -0500 X-MIMETrack: Serialize by Router on D01ML605/01/M/IBM(Release 9.0IF2 |July 03, 2013) at 01/29/2014 03:52:43 PM, Serialize complete at 01/29/2014 03:52:43 PM Content-Type: multipart/alternative; boundary="=_alternative 0072B08185257C6F_=" X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 14012920-7182-0000-0000-000009B374BC X-Virus-Checked: Checked by ClamAV on apache.org --=_alternative 0072B08185257C6F_= Content-Type: text/plain; charset="US-ASCII" Sorry, 1000 columns, each 2K, so each row is 2M. I guess HBase will keep a single KV (i.e., a column rather than a row) in a block, so a row will span multiple blocks? My scan pattern is: I will do range scan, find the matching row keys, and fetch the whole row for each row that matches my criteria. Best regards, Wei --------------------------------- Wei Tan, PhD Research Staff Member IBM T. J. Watson Research Center http://researcher.ibm.com/person/us-wtan From: lars hofhansl To: "user@hbase.apache.org" , Date: 01/29/2014 03:49 PM Subject: Re: larger HFile block size for very wide row? You 1000 columns? Not 1000k = 1m column, I assume. So you'll have 2MB KVs. That's a bit on the large side. HBase will "grow" the block to fit the KV into it. It means you have basically one block per KV. I guess you address these rows via point gets (GET), and do not typically scan through them, right? Do you see any performance issues? -- Lars ________________________________ From: Wei Tan To: user@hbase.apache.org Sent: Wednesday, January 29, 2014 12:35 PM Subject: larger HFile block size for very wide row? Hi, I have a HBase table where each row has ~1000k columns, ~2K each. My table scan pattern is to use a row key filter but I need to fetch the whole row (~1000 k) columns back. Shall I set HFile block size to be larger than the default 64K? Thanks, Wei --------------------------------- Wei Tan, PhD Research Staff Member IBM T. J. Watson Research Center http://researcher.ibm.com/person/us-wtan --=_alternative 0072B08185257C6F_=--