You are not gonna gain much by using Rest service of HBase. You need to use native java api of HBase for gaining performance. Similar to thrift, Rest service also has an extra hop.
Sent from my iPhone > On Jan 21, 2016, at 1:03 AM, Rajeshkumar J <[email protected]> > wrote: > > Hi, > > As you all said I have tried Rest web service using Hbase Java API to > get data from Hbase table but it seems to be slower than that of one using > Hbase thrift server. > > can any one tell how ? > > Thanks > >> On Sat, Jan 16, 2016 at 5:41 PM, Zheng Shen <[email protected]> wrote: >> >> Java API is at least 10 times faster than thrift on Hbase write >> operations based on my experience in production environment (cloudera >> 5.4.7, hbase 1.0.0) >> >> Zheng >> >> ---Original--- >> From: "Vladimir Rodionov "<[email protected]> >> Date: 2016/1/15 06:31:34 >> To: "[email protected]"<[email protected]>; >> Subject: Re: Java API vs Hbase Thrift >> >> >>>> I have to access hbase using Java API will it be fast like thrift. >> >> Bear in mind that when you use Thrift Gateway/Thrift API you access HBase >> RegionServer through the single gateway server, >> when you use Java API - you access Region Server directly. >> Java API is much more scalable. >> >> -Vlad >> >>> On Tue, Jan 12, 2016 at 7:36 AM, Anil Gupta <[email protected]> wrote: >>> >>> Java api should be same or better in performance as compared to Thrift >> api. >>> With Thrift api there is an extra hop. So, most of the time java api >> would >>> be better for performance. >>> >>> Sent from my iPhone >>> >>>> On Jan 12, 2016, at 4:29 AM, Rajeshkumar J < >> [email protected]> >>> wrote: >>>> >>>> Hi, >>>> >>>> I am currently accessing records via Hbase thrift server and it is >> fast. >>>> If I have to access hbase using Java API will it be fast like thrift. >>>> >>>> Thanks >> >>
