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 5298FE3BA for ; Fri, 18 Jan 2013 04:39:58 +0000 (UTC) Received: (qmail 8146 invoked by uid 500); 18 Jan 2013 04:39:55 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 8005 invoked by uid 500); 18 Jan 2013 04:39:55 -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 7992 invoked by uid 99); 18 Jan 2013 04:39:55 -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:39:55 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ramasubramanian.narayanan@gmail.com designates 209.85.223.171 as permitted sender) Received: from [209.85.223.171] (HELO mail-ie0-f171.google.com) (209.85.223.171) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2013 04:39:51 +0000 Received: by mail-ie0-f171.google.com with SMTP id 9so2020030iec.30 for ; Thu, 17 Jan 2013 20:39:31 -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=TOippqVzNCe/usopnmRpr2rY3Ln27EXkNyDLyRQ+RbA=; b=UEkkj6t2mXUpDTTDIDxR0Cn82vzSlYO/X880xbjxNWXxwvzjGEyY3fjVaS9pJOz5Yi acoSs9k1DGkgSTzxRXIoJ5dzlJy1iQezxhQzjbPpS1TD03OqQWd6ayhzIZrBIIei/Wej af313Q03lBMOE1piwcU9lHcplByuZRqW1pV7OugphzlRcUj5msyj6uHDqmfkxip8k0MZ xs1Wk+fKc7fe6M+29vYSQBI330OxUr/2EKKG8TIUpvs8C7iduRTobI4W2t0zBpxXr1QV jE7JkAX27xz5L9OaEl9yYslKE0Rl2WxRC+TbtsW+HW0BYJyBVdNf1puzkIT/1MOa9X+T Sl9w== MIME-Version: 1.0 X-Received: by 10.50.83.162 with SMTP id r2mr955270igy.106.1358483971039; Thu, 17 Jan 2013 20:39:31 -0800 (PST) Received: by 10.42.74.132 with HTTP; Thu, 17 Jan 2013 20:39:30 -0800 (PST) In-Reply-To: References: Date: Fri, 18 Jan 2013 10:09:30 +0530 Message-ID: Subject: Re: How to de-nomarlize for this situation in HBASE Table From: Ramasubramanian Narayanan To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=e89a8f2347cf86e1e604d388b2e8 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f2347cf86e1e604d388b2e8 Content-Type: text/plain; charset=ISO-8859-1 Hi Sonal, In that case, the problem is how to store multiple physical address sets in the same column family.. what rowkey to be used for this scenario.. A Physical address will contain the following fields (need to store multiple physical address like this): Physical address type : Home/office/other/etc Address line1: .. .. Address line 4: State : City: Country: regards, Rams On Fri, Jan 18, 2013 at 10:00 AM, Sonal Goyal wrote: > 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 > > > > > > > > > > --e89a8f2347cf86e1e604d388b2e8--