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 2B638D991 for ; Thu, 11 Oct 2012 04:54:28 +0000 (UTC) Received: (qmail 55852 invoked by uid 500); 11 Oct 2012 04:54:25 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 54563 invoked by uid 500); 11 Oct 2012 04:54:23 -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 54527 invoked by uid 500); 11 Oct 2012 04:54:23 -0000 Delivered-To: apmail-hadoop-hbase-user@hadoop.apache.org Received: (qmail 54521 invoked by uid 99); 11 Oct 2012 04:54:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Oct 2012 04:54:22 +0000 X-ASF-Spam-Status: No, hits=-1.3 required=5.0 tests=MSGID_MULTIPLE_AT,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ramkrishna.vasudevan@huawei.com designates 119.145.14.64 as permitted sender) Received: from [119.145.14.64] (HELO szxga01-in.huawei.com) (119.145.14.64) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Oct 2012 04:54:13 +0000 Received: from 172.24.2.119 (EHLO szxeml213-edg.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.4-GA FastPath queued) with ESMTP id AQK36116; Thu, 11 Oct 2012 12:53:51 +0800 (CST) Received: from SZXEML420-HUB.china.huawei.com (10.82.67.159) by szxeml213-edg.china.huawei.com (172.24.2.30) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 11 Oct 2012 12:52:14 +0800 Received: from blrprnc05ns (10.18.96.94) by szxeml420-hub.china.huawei.com (10.82.67.159) with Microsoft SMTP Server id 14.1.323.3; Thu, 11 Oct 2012 12:52:11 +0800 From: "Ramkrishna.S.Vasudevan" To: CC: References: <0CE69E9126D0344088798A3B7F7F80863A4E222F@szxeml531-mbx.china.huawei.com>, , <0CE69E9126D0344088798A3B7F7F80863A4E2595@szxeml531-mbx.china.huawei.com> In-Reply-To: <0CE69E9126D0344088798A3B7F7F80863A4E2595@szxeml531-mbx.china.huawei.com> Subject: RE: HBase table - distinct values Date: Thu, 11 Oct 2012 10:22:09 +0530 Message-ID: <004901cda76c$2c6deac0$8549c040$@vasudevan@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AQHNptZgF3DpP1CQUE+Vzz4UICnFE5eyfFDW//+U/4CAAWmRKoAADOZg Content-Language: en-us X-Originating-IP: [10.18.96.94] X-CFilter-Loop: Reflected X-Virus-Checked: Checked by ClamAV on apache.org Are you planning to use region splits? Can the rowkey have the deptno? Having dept no in another table, may be having a reverse mapping of deptno to empno may be helpful too if such queries are frequent. Regards Ram > -----Original Message----- > From: Anoop Sam John [mailto:anoopsj@huawei.com] > Sent: Thursday, October 11, 2012 9:32 AM > To: user@hbase.apache.org > Cc: hbase-user@hadoop.apache.org > Subject: RE: HBase table - distinct values > > Hi Ravi > If dept_no is a CF:qualifier, to know all the dept numbers > (distinct or not) you need a full table scan. As Doug said if it is a > frequent online query don't think MR is a good choice.. If the data in > your emp table is huge a full table scan also wont be that good I > feel.... Can you guys think about storing dept number in another > table? If you people need query like select from emp > where dept_no=? (this query also) you can think about creating > secondary index implementation and indexing dept_no... You can use > index table for above query as well as the 1st one you asked about. :) > > -Anoop- > ________________________________________ > From: raviprasad.t@polarisFT.com [raviprasad.t@polarisFT.com] > Sent: Wednesday, October 10, 2012 7:51 PM > To: user@hbase.apache.org > Cc: hbase-user@hadoop.apache.org; user@hbase.apache.org > Subject: RE: HBase table - distinct values > > Hi, > Hbase table name :- emp > Column family :- cf > Under the column family cf we will be having the field name > deptno > > > Regards > Raviprasad. T > Mobile :- 91- 9894769541 > > > -----Anoop Sam John wrote: ----- > To: "user@hbase.apache.org" , "hbase- > user@hadoop.apache.org" > From: Anoop Sam John > Date: 10/10/2012 06:18PM > Subject: RE: HBase table - distinct values > > Hi > Your schema? 'deptno' is a cf:qualifier? > > -Anoop- > ________________________________________ > From: raviprasad.t@polarisFT.com [raviprasad.t@polarisFT.com] > Sent: Wednesday, October 10, 2012 4:29 PM > To: user@hbase.apache.org; hbase-user@hadoop.apache.org > Subject: HBase table - distinct values > > Hi all, > Is it possible to select distinct value from Hbase table. > > Example :- > what is the equivalant code for the below Oracle code in Hbase ? > > Select count (distinct deptno) from emp ; > > Regards > Raviprasad. T > > > This e-Mail may contain proprietary and confidential information and is > sent for the intended recipient(s) only. If by an addressing or > transmission error this mail has been misdirected to you, you are > requested to delete this mail immediately. You are also hereby notified > that any use, any form of reproduction, dissemination, copying, > disclosure, modification, distribution and/or publication of this e- > mail message, contents or its attachment other than by its intended > recipient/s is strictly prohibited. > > Visit us at http://www.polarisFT.com > > > This e-Mail may contain proprietary and confidential information and is > sent for the intended recipient(s) only. If by an addressing or > transmission error this mail has been misdirected to you, you are > requested to delete this mail immediately. You are also hereby notified > that any use, any form of reproduction, dissemination, copying, > disclosure, modification, distribution and/or publication of this e- > mail message, contents or its attachment other than by its intended > recipient/s is strictly prohibited. > > Visit us at http://www.polarisFT.com=