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 40ED9E3A2 for ; Fri, 18 Jan 2013 04:31:13 +0000 (UTC) Received: (qmail 89599 invoked by uid 500); 18 Jan 2013 04:31:11 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 89483 invoked by uid 500); 18 Jan 2013 04:31:11 -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 89468 invoked by uid 99); 18 Jan 2013 04:31:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2013 04:31:10 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sonalgoyal4@gmail.com designates 209.85.223.174 as permitted sender) Received: from [209.85.223.174] (HELO mail-ie0-f174.google.com) (209.85.223.174) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2013 04:31:06 +0000 Received: by mail-ie0-f174.google.com with SMTP id k11so60061iea.5 for ; Thu, 17 Jan 2013 20:30:45 -0800 (PST) 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=BeLgYvLOq94A08tR5Dxj/IuY8V6NdVfmTDyqYIdMzvs=; b=al5zIRt2kV6COA8yAR3gB8/pKpSbx7q1upC6x1KGrWFTu4QQH1YbCb/yL/47F3hqAT gA7+Vrjr1NCnIzsNDGiVqEkmsrCsxUNM3Wbu1872nADVUOpORhYb6uEDw20k8BhyNx+D H0U/r8LOd9NiDzK0LlTIw1JaGpS1VjQnlHQ8rxw6SmyQ0pbQ+obD0Eo3O0kV5ZoFSkNa tN6DJa2VoBd7dIAXOfMCuF62I96yz8S/JbYaAgO+r34R4Ujj3aop8zqPjaJb0lqJ+CKa HoI7CmPnF7JXD7t+6zmiW14TwDxVB8mPo/yvZEOi5zlB/zYBC2qzI65M8wlMYlNw2nv6 SI4A== MIME-Version: 1.0 X-Received: by 10.50.178.10 with SMTP id cu10mr982439igc.75.1358483445819; Thu, 17 Jan 2013 20:30:45 -0800 (PST) Received: by 10.50.202.3 with HTTP; Thu, 17 Jan 2013 20:30:45 -0800 (PST) In-Reply-To: References: Date: Fri, 18 Jan 2013 10:00:45 +0530 Message-ID: Subject: Re: How to de-nomarlize for this situation in HBASE Table From: Sonal Goyal To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=e89a8f839ca138a8f304d3889380 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f839ca138a8f304d3889380 Content-Type: text/plain; charset=ISO-8859-1 How about client id as the rowkey, with column families as physical address, email address, telephone address? within each cf, you could have various qualifiers. For eg in physical address, you could have home Street, office street etc. Best Regards, Sonal Real Time Analytics for BigData Nube Technologies On Fri, Jan 18, 2013 at 9:46 AM, Ramasubramanian Narayanan < ramasubramanian.narayanan@gmail.com> wrote: > Hi Sonal, > > 1. will fetch all demographic details of customer based on client ID > 2. Fetch the particular type of address along with other demographic for a > client.. for example, HOME Physical address or HOME Telephone address or > office Email address etc., > > regards, > Rams > > On Fri, Jan 18, 2013 at 9:29 AM, Sonal Goyal > wrote: > > > What are your data access patterns? > > > > Best Regards, > > Sonal > > Real Time Analytics for BigData > > Nube Technologies > > > > > > > > > > > > > > On Fri, Jan 18, 2013 at 9:04 AM, Ramasubramanian Narayanan < > > ramasubramanian.narayanan@gmail.com> wrote: > > > > > Hi, > > > > > > I have the following relational tables.. I want to denormalize and > bring > > it > > > all into single HBASE table... Pls help how it could be done.. > > > > > > > > > 1. Client Master Table > > > 2. Physical Address Table (there might be 'n' number of address that > can > > be > > > captured against each client ID) > > > 3. Email Address Table (there might be 'n' number of address that can > be > > > captured against each client ID) > > > 4. Telephone Address Table (there might be 'n' number of address that > can > > > be captured against each client ID) > > > > > > > > > For the tables 2 to 4, there are multiple fields like which is the > > Address > > > type (home/office,etc), bad address, good address, communication > address, > > > time to call etc., > > > > > > Please help me to clarify the following : > > > > > > 1. Whether we can bring this to a single HBASE table? > > > 2. Having fields like phone number1, phone number 2 etc. is not an good > > > approach for this scenario... > > > 3. Whether we can have in the same table by populating these multiple > > rows > > > for the same customer with different rowkey? > > > For e.g. > > > For Client Records - Rowkey can be Client Number + DOB > > > For Physical Address - Rowkey can be Client Number + "PHYSICAL" + > > Type > > > of Address > > > For Email Address - Rowkey can be Client Number + "EMAIL" + > Type > > of > > > Address > > > For Telephone Address - Rowkey can be Client Number + "TEL" + > > Type > > > of Address > > > > > > regards, > > > Rams > > > > > > --e89a8f839ca138a8f304d3889380--