Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 57904 invoked from network); 10 Mar 2011 01:47:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Mar 2011 01:47:01 -0000 Received: (qmail 46245 invoked by uid 500); 10 Mar 2011 01:47:00 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 46212 invoked by uid 500); 10 Mar 2011 01:47:00 -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 46204 invoked by uid 500); 10 Mar 2011 01:47:00 -0000 Delivered-To: apmail-hadoop-hbase-user@hadoop.apache.org Received: (qmail 46201 invoked by uid 99); 10 Mar 2011 01:47:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Mar 2011 01:47:00 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cameron.developer@gmail.com designates 209.85.213.48 as permitted sender) Received: from [209.85.213.48] (HELO mail-yw0-f48.google.com) (209.85.213.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Mar 2011 01:46:53 +0000 Received: by ywo32 with SMTP id 32so688349ywo.35 for ; Wed, 09 Mar 2011 17:46:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=M8oRMSagdBVoPt4vTjJ+y/p5LGa+jWvwn3L4JUTwfVo=; b=Yjr8PHR2qjAjJL24Gp5LqNzfaymtWUhhBCnAyLBURNel06P5f2Q/motJJ0Dupgid3Q iS/JIVwctv5P6yc6UkL1y28eqN4mdR2RhKxG14iBs5UWbmdQPNLgPPfGmFF2mJkGcb1D so5bCWwn5vGQy74Zj71/5F3lSdCp/pDE2u4eM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=rxC+u1o40eypsUpnhsJzS4i6CGJjVjNoW4xnedp7MOwynavcBQe8L+Vwe+drUAMAnf B3W2Rof5XuTIiYw73SuoB/GfpaSRHXDT80ayKu0O8xEGxyMCm4xDfgySzp3gaDEaKqeU LLYfYaH/si9MFjQwvkpeupSxtZBbq5wYDZVEk= Received: by 10.236.73.230 with SMTP id v66mr602570yhd.134.1299721593110; Wed, 09 Mar 2011 17:46:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.105.131 with HTTP; Wed, 9 Mar 2011 17:46:13 -0800 (PST) In-Reply-To: References: From: Cameron Leach Date: Wed, 9 Mar 2011 17:46:13 -0800 Message-ID: Subject: Modeling Multi-Valued Fields To: hbase-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=20cf30051392dd4284049e17031e --20cf30051392dd4284049e17031e Content-Type: text/plain; charset=UTF-8 ~resending to hbase-user@hadoop.apache.org~ Is there a best-practice for modeling multi-valued fields (fields that are repeated or collections of fields)? Our current data model allows for a User to store multiple email addresses: User { Integer id; //row key List emails; Email { String type; //home, work, gmail, hotmail, etc... String address; } } So if I setup a 'User' table with an 'Email' column family, how would one support multiple email addresses, storing values for the 'type' and 'address' columns? I've seen it suggested to have dynamic column names, but this doesn't seem practical, unless someone can make it more clear how that strategy would work. Thanks! --20cf30051392dd4284049e17031e--