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 "<vladrodio...@gmail.com> Date: 2016/1/15 06:31:34 To: "user@hbase.apache.org"<user@hbase.apache.org>; 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 <anilgupt...@gmail.com> 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 <rajeshkumarit8...@gmail.com> > 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 >
