Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 80FFA10FFA for ; Mon, 23 Dec 2013 22:56:07 +0000 (UTC) Received: (qmail 10257 invoked by uid 500); 23 Dec 2013 22:56:06 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 10174 invoked by uid 500); 23 Dec 2013 22:56:06 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 10166 invoked by uid 99); 23 Dec 2013 22:56:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Dec 2013 22:56:06 +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 ndimiduk@gmail.com designates 209.85.220.182 as permitted sender) Received: from [209.85.220.182] (HELO mail-vc0-f182.google.com) (209.85.220.182) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Dec 2013 22:56:00 +0000 Received: by mail-vc0-f182.google.com with SMTP id lc6so3030428vcb.41 for ; Mon, 23 Dec 2013 14:55:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=1OZjWmHoxoKK5/IJKnhwBqMZvYGuxnKBebozPbfIehk=; b=BopK9sqG26x2b+x/9pFXMKl1Sda2voljVM4c3qH4vriHLkkx6kORliiSc1kiQ21lrU VYY5ZXor/L5mbOTGV6uHyogTAKkh3AeQbooL8Vl0Rs96ZW5nu9I8tDc3dq+odM/7aUqR 6d6ZwcGE8qQQSz721zzOE5kPyDsAySpsiPxFcBDflCU20Sev9s8omRhBvvnTqwj6Z2TZ sXV+VwENk11nCu5t0cd2STO2SsbyWfdXfitEOiaOVY8xHS2VcWGzlpN/bh3y3zJCEkmv KfCSLP7dq8MsqDqEXGQwDwLJG501GmzZGy1k1sAsT/MII8Xq/hl7Hmf9jr++mdg+TJs9 CrVg== X-Received: by 10.58.67.9 with SMTP id j9mr14866772vet.3.1387839339519; Mon, 23 Dec 2013 14:55:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.58.161.100 with HTTP; Mon, 23 Dec 2013 14:55:19 -0800 (PST) In-Reply-To: References: <2013122123172401234313@126.com> <201312221107523483230@126.com> From: Nick Dimiduk Date: Mon, 23 Dec 2013 14:55:19 -0800 Message-ID: Subject: Re: Re: About HBASE-3149 To: hbase-dev Content-Type: multipart/alternative; boundary=047d7b339e07d667b704ee3b8607 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b339e07d667b704ee3b8607 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Committed via HBASE-10234. On Mon, Dec 23, 2013 at 2:35 PM, Stack wrote: > I'd do non-relational database as per Jon... just make the change Nick...= . > I'll push out later no worries (it is a bit of a pain... learn it by all > means but this is not cause enough) > > > On Mon, Dec 23, 2013 at 1:03 PM, Jonathan Hsieh wrote: > > > I usually say, non-relational database. > > > > Jon. > > > > > > On Mon, Dec 23, 2013 at 11:52 AM, Nick Dimiduk > wrote: > > > > > On Sat, Dec 21, 2013 at 7:07 PM, =E4=B9=83=E5=B2=A9 wrote: > > > > > > > Hello, Thank you for your reply. > > > > If use only 1 or 2 CFs, why Hbase say it's a column data store? It'= s > > > > actually row-based data store!! > > > > > > > > > > Nit: I don't think HBase claims to be a column-oriented store. > > > "Column-family," yes... But now that I write this, I see right on the > > > project homepage: "Apache HBase is an open-source, distributed, > > versioned, > > > *column-oriented* store modeled after ..." (emphasis my own). > > > > > > From: Andrew Purtell > > > > Date: 2013-12-22 04:26 > > > > To: dev@hbase.apache.org; sohomodern > > > > Subject: Re: About HBASE-3149 > > > > Bear in mind that how many files you'll have open simultaneously is= a > > > > function of number of regions, number of column families, and how > > > > compaction organizes the HBase files on disk (the strategy in effec= t > > and > > > > its parameters, the current ingest rate, and so on). You call > ballpark > > > this > > > > as such: If you have one column family in a table, and store data > into > > > all > > > > the regions, then you will have one file open on the cluster per > > region, > > > or > > > > more. If you have 100,000 column families in a table, and store dat= a > > into > > > > all the regions and CFs, then you will have 100,000 files open on t= he > > > > cluster per region, *or more*. You will run into OS and HDFS levels > > > > attempting this, I don't recommend it. > > > > > > > > > > > > I don't think any reasonable schema design needs produce a > requirement > > > for > > > > 100,000 column *families*. You can have any number of keys with > > > > : in a column family, varying the to > > > 100,000 > > > > or 1,000,000 or more unique values is no problem. Can you say more > > about > > > > what you are trying to accomplish? > > > > > > > > > > > > > > > > On Sat, Dec 21, 2013 at 7:17 AM, =E4=B9=83=E5=B2=A9 wrote: > > > > > > > > Hi, > > > > Can anybody tell me if future HBase release will integrate 3149 > for > > > > Make flush decisions per column family=EF=BC=9F > > > > > > > > By the way, for current HBase, if the simultaneous flush is the > only > > > > issue? I mean, to create 100000 CFs will not be a problem, right? > > > > > > > > Thanks in advance! > > > > > > > > > > > > > > > > > > > > > > > > N.Y. > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Best regards, > > > > > > > > - Andy > > > > > > > > Problems worthy of attack prove their worth by hitting back. - Piet > > Hein > > > > (via Tom White) > > > > > > > > > > > > > > > -- > > // Jonathan Hsieh (shay) > > // Software Engineer, Cloudera > > // jon@cloudera.com > > > --047d7b339e07d667b704ee3b8607--