Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 583D21185E for ; Tue, 8 Jul 2014 17:06:30 +0000 (UTC) Received: (qmail 92187 invoked by uid 500); 8 Jul 2014 17:06:26 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 92072 invoked by uid 500); 8 Jul 2014 17:06:25 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 91929 invoked by uid 99); 8 Jul 2014 17:06:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jul 2014 17:06:25 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bbeaudreault@hubspot.com designates 74.125.149.143 as permitted sender) Received: from [74.125.149.143] (HELO na3sys009aog130.obsmtp.com) (74.125.149.143) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jul 2014 17:06:23 +0000 Received: from mail-ve0-f177.google.com ([209.85.128.177]) (using TLSv1) by na3sys009aob130.postini.com ([74.125.148.12]) with SMTP ID DSNKU7wk9R96oGCKzqOkNyVImw1zmY6k5gUB@postini.com; Tue, 08 Jul 2014 10:05:58 PDT Received: by mail-ve0-f177.google.com with SMTP id i13so5922382veh.36 for ; Tue, 08 Jul 2014 10:05:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=pP3U8HPtfNT3STFQ99LqRiJ/HXT3aaaWavnZxU8318U=; b=KIZMyQeCNIk9166jMcdFAG3wD5r7e+x3g+TYsllltY8o2rykpOO2Y9NdpckmPybrGh akBJIpzoZmDbZNM/f958kmV6wg5F6BeOL+UvV6whv6SBRIerYBCf4B/bMiHD8T04AmI8 Wd1rN2S08RlUpDjtOFHA0f5zmzcJLGxIjlOr569k8v0PSRmBgLtPBUeBPm23N/pMrR6n VqKhBpQS0sDBvJopKmv3d9ynO/QIjRKcTAnd+dULyxGs1o2n7ytZk65I7L2kkzmVH70b wvZU7IOM2dAfnfaPBdzA2IU1gJzHmU1LNKtZ62c48xn2lrVu0baMYazm6wuSSaBO8pPI 4LAg== X-Gm-Message-State: ALoCoQk7zZ0ZsnpOEYaary7DDWgysmylgH2O2T7AnWVLYQFTCzHIB65Cjmw8SJK9L43F04l+4L51bpxnJuL6su+50ptCUNe1TfIGzR2Nu4AIa+OrxYoVRbnrcpXm4Eeo6rI2XBJUEpi0 X-Received: by 10.58.245.194 with SMTP id xq2mr35095209vec.26.1404839157033; Tue, 08 Jul 2014 10:05:57 -0700 (PDT) X-Received: by 10.58.245.194 with SMTP id xq2mr35095201vec.26.1404839156910; Tue, 08 Jul 2014 10:05:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.221.19.197 with HTTP; Tue, 8 Jul 2014 10:05:36 -0700 (PDT) In-Reply-To: References: <869970D71E26D7498BDAC4E1CA92226B94064E7A@MBX021-E3-NJ-2.exch021.domain.local> <869970D71E26D7498BDAC4E1CA92226B94064EEA@MBX021-E3-NJ-2.exch021.domain.local> <869970D71E26D7498BDAC4E1CA92226B94064F3F@MBX021-E3-NJ-2.exch021.domain.local> From: Bryan Beaudreault Date: Tue, 8 Jul 2014 13:05:36 -0400 Message-ID: Subject: Re: HBase metadata To: "hbase-user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=047d7bd6b7bcea28a204fdb19a20 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bd6b7bcea28a204fdb19a20 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable At HubSpot we write all of our own code using the normal Java API for Scans, Gets, etc. We built a lightweight internal framework around this to enforce some standards. Some people also use the Thrift interface and code in, for example, python. I doubt many (or any) people use Hive as the interface. On Tue, Jul 8, 2014 at 1:01 PM, Martin, Nick wrote: > Can=E2=80=99t speak for the rest of the Hadoop community but we use Ling= ual. Not > sure if that=E2=80=99s common or not. > > > > Maybe worth posting the same question to @hbase. > > > > *From:* John Lilley [mailto:john.lilley@redpoint.net] > *Sent:* Tuesday, July 08, 2014 12:57 PM > > *To:* user@hadoop.apache.org > *Subject:* RE: HBase metadata > > > > Sorry to be rude, but what does everyone actually use now? We are an ISV > and need to support the most common access pattern. > > john > > > > *From:* Martin, Nick [mailto:NiMartin@pssd.com ] > *Sent:* Tuesday, July 08, 2014 10:53 AM > *To:* user@hadoop.apache.org > *Subject:* RE: HBase metadata > > > > Have you looked @ Lingual? > > > > *From:* John Lilley [mailto:john.lilley@redpoint.net > ] > *Sent:* Tuesday, July 08, 2014 12:43 PM > *To:* user@hadoop.apache.org > *Subject:* RE: HBase metadata > > > > Those look intriguing. But what do people actually use today? Is it all > application-specific coding? Hive? > > John > > > > > > *From:* Mirko K=C3=A4mpf [mailto:mirko.kaempf@gmail.com > ] > *Sent:* Tuesday, July 08, 2014 10:12 AM > *To:* user@hadoop.apache.org > *Subject:* Re: HBase metadata > > > > Hi John, > > I suggest the project: http://www.kiji.org/ > > > > or even the brand new: http://phoenix.apache.org/ > > Cheers, > > Mirko > > > > > 2014-07-08 16:05 GMT+00:00 John Lilley : > > Greetings! > > > > We would like to support HBase in a general manner, having our software > connect to any HBase table and read/write it in a row-oriented fashion. > However, as we explore HBase, the raw interface is at a very low level -- > basically a map from binary record keys to named columns. So my question > about metadata standards. What do users mostly do to use HBase for > row-oriented access? It is always going through Hive? > > > > Thanks > > john > > > > > --047d7bd6b7bcea28a204fdb19a20 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
At HubSpot we write all of our own code using the normal J= ava API for Scans, Gets, etc. =C2=A0We built a lightweight internal framewo= rk around this to enforce some standards.

Some people al= so use the Thrift interface and code in, for example, python. =C2=A0I doubt= many (or any) people use Hive as the interface.


On Tue,= Jul 8, 2014 at 1:01 PM, Martin, Nick <NiMartin@pssd.com> wr= ote:

Can=E2=80=99t speak for the r= est of the Hadoop community but we use Lingual. Not sure if that=E2=80=99s = common or not.

=C2=A0

Maybe worth posting the same = question to @hbase.

=C2=A0

From: John Lil= ley [mailto:j= ohn.lilley@redpoint.net]
Sent: Tuesday, July 08, 2014 12:57 PM


To: user= @hadoop.apache.org
Subject: RE: HBase metadata

=C2=A0

Sorry to be rude, but wha= t does everyone actually use now?=C2=A0 We are an ISV and need to support t= he most common access pattern.

john=

=C2=A0

From: Martin, = Nick [mailto:NiMarti= n@pssd.com]
Sent: Tuesday, July 08, 2014 10:53 AM
To: user= @hadoop.apache.org
Subject: RE: HBase metadata

=C2=A0

Have you looked @ Lingual?=

=C2=A0

From: John Lil= ley [mailto:j= ohn.lilley@redpoint.net]
Sent: Tuesday, July 08, 2014 12:43 PM
To: user= @hadoop.apache.org
Subject: RE: HBase metadata

=C2=A0

Those look intriguing.=C2= =A0 But what do people actually use today?=C2=A0 Is it all application-spec= ific coding?=C2=A0 Hive?

John=

=C2=A0

=C2=A0

From: Mirko K= =C3=A4mpf [mail= to:mirko.kaempf@gmail.com]
Sent: Tuesday, July 08, 2014 10:12 AM
To: user= @hadoop.apache.org
Subject: Re: HBase metadata

=C2=A0

Hi John,

I suggest the project: http://www.kiji.org/

=C2=A0

or even the brand new= : http://phoenix.apache.org/

Cheers,

Mirko
=C2=A0

=C2=A0<= /p>

2014-07-08 16:05 GMT+00:00 John Lilley <john.lilley@redpoint= .net>:

Greetings!

=C2=A0

We would like to support HBase in a general manner, = having our software connect to any HBase table and read/write it in a row-o= riented fashion.=C2=A0 However, as we explore HBase, the raw interface is at a very low level -- basically a map from binary record= keys to named columns.=C2=A0 So my question about metadata standards.=C2= =A0 What do users mostly do to use HBase for row-oriented access?=C2=A0 It = is always going through Hive?

=C2=A0

Thanks

john

=C2=A0

=C2=A0


--047d7bd6b7bcea28a204fdb19a20--