Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A84692004F1 for ; Wed, 30 Aug 2017 18:15:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A69E21696BC; Wed, 30 Aug 2017 16:15:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1F67B1696BA for ; Wed, 30 Aug 2017 18:15:13 +0200 (CEST) Received: (qmail 95788 invoked by uid 500); 30 Aug 2017 16:15:12 -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 95777 invoked by uid 99); 30 Aug 2017 16:15:12 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Aug 2017 16:15:12 +0000 Received: from hw10447.local (unknown [167.102.188.146]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 351F21A02CF for ; Wed, 30 Aug 2017 16:15:10 +0000 (UTC) Subject: Re: Need help with Row Key design To: user@hbase.apache.org References: <1504095687623-0.post@n3.nabble.com> From: Josh Elser Message-ID: <408c6573-b77b-acad-a5af-8de1019c65c1@apache.org> Date: Wed, 30 Aug 2017 12:15:10 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:56.0) Gecko/20100101 Thunderbird/56.0 MIME-Version: 1.0 In-Reply-To: <1504095687623-0.post@n3.nabble.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit archived-at: Wed, 30 Aug 2017 16:15:14 -0000 You may find Apache Phoenix to be of use as you explore your requirements. Phoenix provides a much higher-level API which provides logic to build composite rowkeys (e.g. primary key constraints over multiple columns) for you automatically. This would help you iterate much faster as you better understand the storage and query requirements of your application. On 8/30/17 8:21 AM, deepaksharma25 wrote: > Hello, > I am new to HBase DB and currently evaluating it for one of the requirement > we have from Customer. > We are going to write TBs of data in HBase daily and we need to fetch > specifc data based on filter. > > I came to know that it is very important to design the row key in such a > manner, so that it effectively uses it to fetch the data from the specific > node instead of scanning thru all the records in the database, based on the > type of row key we design. > > The problem with our requirement is that, we don't have any specific field > which can be used to define the rowkey. We have around 7-8 fields available > on the frontend, which can be used to filter the records from HBase. > > Can you please suggest, what should be the design of my row key, which will > help in faster retrieval of the data from TBs of data? > Attaching here the sample screen I am referring in this > . > > Thanks, > Deepak Sharma > > > > -- > Sent from: http://apache-hbase.679495.n3.nabble.com/HBase-User-f4020416.html >