Return-Path: 
 <user-return-16044-apmail-hadoop-common-user-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-user-archive@www.apache.org
Delivered-To: apmail-hadoop-common-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 9359D115BF
	for <apmail-hadoop-common-user-archive@www.apache.org>;
 Tue,  8 Jul 2014 16:12:39 +0000 (UTC)
Received: (qmail 6573 invoked by uid 500); 8 Jul 2014 16:12:35 -0000
Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org
Received: (qmail 6468 invoked by uid 500); 8 Jul 2014 16:12:34 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 5996 invoked by uid 99); 8 Jul 2014 16:12:34 -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 16:12:34 +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 (nike.apache.org: domain of mirko.kaempf@gmail.com
 designates 209.85.220.45 as permitted sender)
Received: from [209.85.220.45] (HELO mail-pa0-f45.google.com) (209.85.220.45)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jul 2014 16:12:33 +0000
Received: by mail-pa0-f45.google.com with SMTP id rd3so7544303pab.4
        for <user@hadoop.apache.org>; Tue, 08 Jul 2014 09:12:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=J5jbc3XnWr2finU9XlBEoiKphI2xx6pzuQlwZNlAN1A=;
        b=MbZSnGA+6K5Lj9y1FH3qexMCfIrnxGWq5uuOiLFWa+K88N8H8Ne2OAkzu/EWDIcuTM
         3oWVAIclFSei8lkvIIaVq5SCg9T4pwUK6YTxgxCGLYbXxYbSbu/EaIdNfr1rifTR2CWE
         S/pt2M27rOzgJWeCG9h9bSenXLGufGTRaPT3XvFU0oRH5mNElBUr5CK09ha/omP7/tME
         hJDGMUWx+5RSnaS2kUxrBX0OyfVEF5KvcRlRpAJ3nKjyja9eQvSLTneGjNDZo9m2Nevg
         8uNd8klohcUtq0hZ6LEA/pZODBEw8ix7bdR7wySWiF0/JYtW/zeZ7Ox6Y4zlb9ezX2N1
         Wz2w==
X-Received: by 10.68.138.227 with SMTP id qt3mr36057192pbb.6.1404835927541;
 Tue, 08 Jul 2014 09:12:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.179.75 with HTTP; Tue, 8 Jul 2014 09:11:47 -0700 (PDT)
In-Reply-To: 
 <869970D71E26D7498BDAC4E1CA92226B94064E7A@MBX021-E3-NJ-2.exch021.domain.local>
References: 
 <869970D71E26D7498BDAC4E1CA92226B94064E7A@MBX021-E3-NJ-2.exch021.domain.local>
From: =?UTF-8?B?TWlya28gS8OkbXBm?= <mirko.kaempf@gmail.com>
Date: Tue, 8 Jul 2014 16:11:47 +0000
Message-ID: 
 <CALKHTG9XUHmxawY2ZoiO=TMFBs1E_DZA7EWZAxo3uy1O9Oyxnw@mail.gmail.com>
Subject: Re: HBase metadata
To: "user@hadoop.apache.org" <user@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=e89a8f83a5e56dcf3f04fdb0da63
X-Virus-Checked: Checked by ClamAV on apache.org

--e89a8f83a5e56dcf3f04fdb0da63
Content-Type: text/plain; charset=UTF-8

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 <john.lilley@redpoint.net>:

>  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
>
>
>

--e89a8f83a5e56dcf3f04fdb0da63
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div>Hi John,<br><br></div>I suggest t=
he project: <a href=3D"http://www.kiji.org/">http://www.kiji.org/</a><br></=
div><br></div>or even the brand new: <a href=3D"http://phoenix.apache.org/"=
>http://phoenix.apache.org/</a><br>

<br></div>Cheers,<br></div>Mirko<br>=C2=A0<br></div><div class=3D"gmail_ext=
ra"><br><br><div class=3D"gmail_quote">2014-07-08 16:05 GMT+00:00 John Lill=
ey <span dir=3D"ltr">&lt;<a href=3D"mailto:john.lilley@redpoint.net" target=
=3D"_blank">john.lilley@redpoint.net</a>&gt;</span>:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">Greetings!<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">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 a=
t a very low level -- basically a map from
 binary record keys to named columns.=C2=A0 So my question about metadata s=
tandards.=C2=A0 What do users mostly do to use HBase for row-oriented acces=
s?=C2=A0 It is always going through Hive?<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Thanks<span class=3D"HOEnZb"><font color=3D"#888888"=
><u></u><u></u></font></span></p><span class=3D"HOEnZb"><font color=3D"#888=
888">
<p class=3D"MsoNormal">john<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</font></span></div>
</div>

</blockquote></div><br></div>

--e89a8f83a5e56dcf3f04fdb0da63--