Igor, What does this really buy you?
I'm trying to figure out a use case that would show a benefit from just fetching the rows individually. Since the rows are not contiguous, the odds of the next row you want being in cache are going to slight to most likely not. ;-) Can you give a use case where having a 'multi-get' will make life easier? Thx -Mike > Date: Wed, 25 Aug 2010 07:17:13 +0600 > Subject: Re: Best way to get multiple non-sequential rows > From: [email protected] > To: [email protected] > > Thanks Igor, I will have a look at it. > > /Imran > > On Tue, Aug 24, 2010 at 10:36 PM, Igor Ranitovic <[email protected]> wrote: > > Take a look at > > https://issues.apache.org/jira/browse/HBASE-1845 > > > > As an HBase user, multi gets is something that I have been looking forward > > to for some time now. If there is enough interest it would be great if this > > becomes part of 0.90. > > > > Take care, > > i. > > > > Imran M Yousuf wrote: > >> > >> Hi, > >> > >> I am using the HBase client API to interact with HBase. I have noticed > >> that HTableInterface has operations such as put(List<Put>), > >> delete(List<Delete>), but there is no similar method for Get. Using > >> scan it is possible to load a range of rows, i.e. sequential rows. My > >> question is - > >> how would it be most efficient to load N non-sequential rows? > >> > >> Currently I am using get(Get) method N times. > >> > > > > > > > > -- > Imran M Yousuf > Blog: http://imyousuf-tech.blogs.smartitengineering.com/ > Mobile: +880-1711402557
