Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of john.lilley@redpoint.net
 designates 206.225.164.221 as permitted sender)
From: John Lilley <john.lilley@redpoint.net>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Subject: Metadata conventions/tools
Thread-Topic: Metadata conventions/tools
Thread-Index: Ac+a0AFYbjawpmAHSY2nOFFJqlm+jw==
Date: Tue, 8 Jul 2014 18:16:47 +0000
Message-ID: 
 <869970D71E26D7498BDAC4E1CA92226B94065055@MBX021-E3-NJ-2.exch021.domain.local>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_869970D71E26D7498BDAC4E1CA92226B94065055MBX021E3NJ2exch_"
MIME-Version: 1.0

--_000_869970D71E26D7498BDAC4E1CA92226B94065055MBX021E3NJ2exch_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Greetings!  We are an ISV of ETL/DI/DQ software and desire to support conne=
ctions to HBase for "classic tabular" data like one would store in an RDBMS=
.  To that end, I am trying to better understand how people typically use H=
Base to store this type of data.  Hive appears to wrap HBase and provide a =
meta-data layer, and users on @hadoop have commented that Phoenix and Lingu=
al are also used, as well as various home-grown solutions.  But we're reall=
y interested in the most common uses and conventions.  Can you comment on w=
hat "most people" actually use in production.  We are not really bleeding-e=
dge (other than running in Hadoop, which I suppose makes us bleeding edge),=
 in the sense that our customers tend to come from a server/RDBMS world and=
 are very comfortable with that paradigm.
Thanks,
John


--_000_869970D71E26D7498BDAC4E1CA92226B94065055MBX021E3NJ2exch_--