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 3FD99FD33 for ; Wed, 3 Apr 2013 14:24:16 +0000 (UTC) Received: (qmail 23028 invoked by uid 500); 3 Apr 2013 14:24:14 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 22978 invoked by uid 500); 3 Apr 2013 14:24:13 -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 22960 invoked by uid 99); 3 Apr 2013 14:24:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Apr 2013 14:24:13 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.215.48 as permitted sender) Received: from [209.85.215.48] (HELO mail-la0-f48.google.com) (209.85.215.48) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Apr 2013 14:24:06 +0000 Received: by mail-la0-f48.google.com with SMTP id fq13so1478511lab.21 for ; Wed, 03 Apr 2013 07:23:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=0AyK0KP06Z4VRw8VX9fS00WUdLd0aK2s4Z7ERutFAYk=; b=sd5fVPKn3B7Oqtlz5D9vIykMK+QuofPQRI2489P+ygA76XZoWaRxgTq2qD07JAgIbD FZzDkC6bwKMXHwM0fZXp6ZiAgjWZJ5rIH5Uxk942+Ab9nO/ijxgKDvc0J36BUpjLy1VC /sOpxfW1xSmTf3ssv57fxhRJuR0h0hXLiILIXA8UOwgo4EkX34JSXG5lxtIGzD//xQgk veqUUWOCjTikDJi8AkTG0mVl23JRIYD7Ay0AAZWZ+DlgNltJcCPUhwk7WXwh+9+Bjq13 ZDpAGs7cK5GqJly1RlORHT750UeiHcp1GnEKEnXnPTsD0re4pwyjBTo3UzAThP5tuB+T 3WAQ== MIME-Version: 1.0 X-Received: by 10.112.20.106 with SMTP id m10mr1245864lbe.8.1364999026306; Wed, 03 Apr 2013 07:23:46 -0700 (PDT) Received: by 10.112.84.133 with HTTP; Wed, 3 Apr 2013 07:23:46 -0700 (PDT) In-Reply-To: References: <198BB82D-110F-4A60-99A0-FAB937C503FA@gmail.com> Date: Wed, 3 Apr 2013 07:23:46 -0700 Message-ID: Subject: Re: should i use compression? From: Ted Yu To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=14dae94734b314f7db04d9759a13 X-Virus-Checked: Checked by ClamAV on apache.org --14dae94734b314f7db04d9759a13 Content-Type: text/plain; charset=ISO-8859-1 Another commonly used encoding is FAST_DIFF Cheers On Wed, Apr 3, 2013 at 7:18 AM, Prakash Kadel wrote: > Thanks, > is there any specific compression that is recommended of the use case > i have? > Since my values are all null will compression help? > > I am thinking of using prefix data_block_encoding.. > Sincerely, > Prakash Kadel > > > On Apr 3, 2013, at 10:55 PM, Ted Yu wrote: > > > You should use data block encoding (in 0.94.x releases only). It is > helpful > > for reads. > > > > You can also enable compression. > > > > Cheers > > > > > > On Wed, Apr 3, 2013 at 6:42 AM, Prakash Kadel >wrote: > > > >> Hello, > >> I have a question. > >> I have a table where i store data in the column qualifiers(the values > >> itself are null). > >> I just have 1 column family. > >> The number of columns per row is variable (1~ few thousands) > >> > >> Currently i don't use compression or the data_block_encoding. > >> > >> Should i? > >> I want to have faster reads. > >> > >> Please suggest. > >> > >> > >> Sincerely, > >> Prakash Kadel > > --14dae94734b314f7db04d9759a13--