You can access HBase from MapReduce, yes. It depends on what you are doing as to which you'd use.
If you context is MapReduce and your source data is in HBase or you want to put the product of the MapReduce job into hbase, then you'd use the HBase MapReduce hookups. Otherwise, go via the HBase APIs (The REST server telegraphs the HBase API out into the world of REST). St.Ack On Tue, Nov 10, 2009 at 1:25 PM, Zhenyu Zhong <[email protected]>wrote: > Stack, > > Thank you very much for your reply. > > It seems there are two ways to access HBase. > One is Mapreduce, the other is a direct way provided by HBase. > May I ask which one is more efficient? In what kind of circumstances do we > need either of these two approaches? > Is REST more efficient than MapReduce? > > thanks > zhenyu > > > On Tue, Nov 10, 2009 at 4:06 PM, stack <[email protected]> wrote: > > > On Tue, Nov 10, 2009 at 1:01 PM, Zhenyu Zhong <[email protected] > > >wrote: > > > > > Hi, > > > > > > I noticed that there is a HBase Rest service which provides nice > features > > > that directly talks to HBase. > > > Does it run MR under the hood? > > > > > > > No. MR is not us. Thats the mapreduce project. > > > > The REST project gives you access to hbase. You can get, put, delete and > > scan rows in an HBase table. Nothing to do with MapReduce. > > > > St.Ack > > >
