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 D3CB6D397 for ; Wed, 1 Aug 2012 13:26:17 +0000 (UTC) Received: (qmail 15606 invoked by uid 500); 1 Aug 2012 13:26:16 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 15568 invoked by uid 500); 1 Aug 2012 13:26:15 -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 15560 invoked by uid 99); 1 Aug 2012 13:26:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2012 13:26:15 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of alex.baranov.v@gmail.com designates 209.85.161.169 as permitted sender) Received: from [209.85.161.169] (HELO mail-gg0-f169.google.com) (209.85.161.169) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2012 13:26:09 +0000 Received: by ggm4 with SMTP id 4so8655269ggm.14 for ; Wed, 01 Aug 2012 06:25:48 -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=lqxGO/h5LT7EcmpbpzvkM3so4lRjDx2HTouvbWgho9U=; b=ZTKsxVq3CANIEiW5hrtwv0B/uNzmdd4V+ECOfMzAKDtF8LZUL3sUmXyREVv9W2pjDV SBE62WuDx1yYE6xnyGQuihK2axckI0DUVt9H+bjgNfZZuFpPFY0jwNvi5Y70FNuBsR3f hBklFxfisADfLtj5AHEWX0msL+6sltF2D9W+BXIXvHBFa2756Nz7O+PVBElWGrj77+ST Y/iDQxekMXdsGc8xbWwAWMxJXIwPCymKVWrHcu5vkfQnGDhYpdAIyh0dJ1CdhuI3ub3I GYkJEPPsBWccfUcwIXENbXdZ6E9ujJVlGneBhPGdzOFcjO8qENhfrBx85KG4ZmO2gT4D quGg== MIME-Version: 1.0 Received: by 10.50.170.39 with SMTP id aj7mr4032129igc.32.1343827548502; Wed, 01 Aug 2012 06:25:48 -0700 (PDT) Received: by 10.50.111.103 with HTTP; Wed, 1 Aug 2012 06:25:48 -0700 (PDT) In-Reply-To: References: Date: Wed, 1 Aug 2012 09:25:48 -0400 Message-ID: Subject: Re: Multiple CF and versions From: Alex Baranau To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=e89a8f235411aaf97404c6343bdc --e89a8f235411aaf97404c6343bdc Content-Type: text/plain; charset=ISO-8859-1 These questions were raised many times in this ML and in other sources (blogs, etc.). You can find them with a little effort. Alex Baranau ------ Sematext :: http://blog.sematext.com/ :: Hadoop - HBase - ElasticSearch - Solr On Wed, Aug 1, 2012 at 1:33 AM, Mohammad Tariq wrote: > Hello Mohit, > > It is advised not to go above two or three column families. > This is because, when we have many column families, the flushing and > compaction can cause too many needless i/o operations, thus reducing > the performance. > > As far as versions are concerned, default value is 3. Although > we can change it as per our need, but it is not recommended to set the > number of max versions to an exceedingly high level because this will > increase size of the StoreFile greatly. > > Regards, > Mohammad Tariq > > > On Wed, Aug 1, 2012 at 10:10 AM, Mohit Anchlia > wrote: > > Are there any disadvantages of: > > > > 1. using multiple column families in a table > > 2. using multiple versions of a columns > -- Alex Baranau ------ Sematext :: http://blog.sematext.com/ :: Hadoop - HBase - ElasticSearch - Solr --e89a8f235411aaf97404c6343bdc--