Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 36690 invoked from network); 22 Sep 2009 17:30:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Sep 2009 17:30:51 -0000 Received: (qmail 91795 invoked by uid 500); 22 Sep 2009 17:30:50 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 91765 invoked by uid 500); 22 Sep 2009 17:30:50 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 91755 invoked by uid 99); 22 Sep 2009 17:30:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Sep 2009 17:30:50 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ryanobjc@gmail.com designates 209.85.210.197 as permitted sender) Received: from [209.85.210.197] (HELO mail-yx0-f197.google.com) (209.85.210.197) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Sep 2009 17:30:42 +0000 Received: by yxe35 with SMTP id 35so5545911yxe.2 for ; Tue, 22 Sep 2009 10:30:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=aLGZRmbZ4MJxbLPHKY6PgOVygy9sDAlBVyS7/odLJK8=; b=qzJRYBalcNIuqVHK1G/DeuDEozZo6AtBK8FW2CBkOz9czwePOfTt7/wV6QCTDXYP63 PMjs4eJlCszbMnvRmDbK012jb/tmysBZcZC0Z7JxTjKgOKbZkn+WmNmyzYHY4U1ZRDCJ SB1zvg/ggyrrrDMLzbsuUYbzR+wiIuoR3wCEs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=odOy3F/ZFr23tUSMF1951E4mzV1GnTdHBQXGpOUrUmnzcPL7jNLAH3a+E6LY6pkEdQ dxt2Ki2ts3KU9mdMkkx43QPFHsYUrLhRbdRF5kHzQ9eZ4cy/MbmULnVh9AAINYHSPyJ6 aJCEux2LSMO6hCONj9vWf9wMKbodmjzeB9vSY= MIME-Version: 1.0 Received: by 10.150.44.20 with SMTP id r20mr2332263ybr.18.1253640622000; Tue, 22 Sep 2009 10:30:22 -0700 (PDT) In-Reply-To: <78568af10909221027y2c4da755u228714b0172f7589@mail.gmail.com> References: <25530827.post@talk.nabble.com> <7c962aed0909221023o424f8c45nbc301ec254e1d507@mail.gmail.com> <78568af10909221027y2c4da755u228714b0172f7589@mail.gmail.com> Date: Tue, 22 Sep 2009 10:30:21 -0700 Message-ID: <78568af10909221030x1c5716ct98a689a06c74f9af@mail.gmail.com> Subject: Re: Best-practice/design query for storing a list/array of values From: Ryan Rawson To: hbase-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=000e0cd5f14cf34c1904742df3b5 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd5f14cf34c1904742df3b5 Content-Type: text/plain; charset=ISO-8859-1 Serializing even a large list into 1 column is not a bad thing necessairly. The thing is when you update that column, you have to rewrite the whole thing. If you expect lots of items and a frequent update it might be better to store each item in a column as stack says above. Another question you can ask is "does my app retrieve this list as a unit always?". If so, and the update rate is not high, a serialized format may be the most efficient route. It all just depends on your app read/write patterns. Good luck! On Sep 22, 2009 10:24 AM, "stack" wrote: Would a family devoted to your list -- called 'list'! -- work for you? You could get individual members of the list by doing list:membername or get them all by getting all elements of the family, etc. St.Ack On Tue, Sep 22, 2009 at 9:57 AM, Keith Thomas wrote: > > I have a family which contains an array, or list, of values. I don't mind > whether it is an ar... --000e0cd5f14cf34c1904742df3b5--