So, is scanner a worthwhile method to use to get a bunch of rows that might be random?
-Jack On Fri, Dec 17, 2010 at 5:06 PM, Ryan Rawson <[email protected]> wrote: > The multi interface in 0.90 will minimize rpc calls from the client to the > region server. This isn't exposed in the thrift api but would be trivial to > do so. > On Dec 17, 2010 4:53 PM, "Jack Levin" <[email protected]> wrote: >> So the language in question for a client is not in question. Rather >> the connector to hbase. The end goal is to be able to say send only 5 >> GETs to get 1000 records quickly, rather then sending 1000 GETs to get >> 1000 records slowly. So, besides the raw api functionality via Java, >> I assume there is no multi-get in REST? >> >> So, the design might have to look like this. Create a connector to >> HBASE thats loaded by Jetty, and have it act as a client face API that >> would get a string of key to run GETs from. Example: >> "GET /connector/table'{1,11,23,17,180,533,N,..}" (where N is a key) >> is a query that will run multi-get via the connector and return all >> values rapidly. Another question is, have anyone done a sort of >> connector before? >> >> -Jack >> >> On Fri, Dec 17, 2010 at 3:56 PM, Andrew Purtell <[email protected]> > wrote: >>>> We will have php querying hbase over tcp, and we need a >>>> connector on the hbase end to return content the fastest >>>> way possible >>> >>> Typically the Thrift connector is used for this. >>> >>> - Andy >>> >>> >>> >>> >>> >
