You don't need to take a skeptical approach; The discussion can be resolved itself into an argument. Please do discuss with hbase members. :)
On Tue, Apr 22, 2008 at 1:28 PM, Bryan Duxbury <[EMAIL PROTECTED]> wrote: > You're talking about a projection of sorts, right? > > Certainly I think it's doable. However, I would like to know why you'd want > to do this instead of just using scanners the way they are now. I would go > so far as saying that this IS what scanners do now. The only difference that > I can think of would be returning more than one row at a time. > > Am I missing any features you would like to exist? Would something in the > client API make it very different? How would you address the > memory/performance issues that would arise? > > -Bryan > > > > On Apr 21, 2008, at 8:04 PM, Edward J. Yoon wrote: > > > > > > > > > > Retrieve a whole range of rows at once? > > > > > > > > > > > Yo, Do you think it's possible? > > I just mean the formed table by selecting certain rows and columns (or > > version) from a big table. > > > > On Tue, Apr 22, 2008 at 1:00 AM, Bryan Duxbury <[EMAIL PROTECTED]> wrote: > > > > > What would getSubTable do? Retrieve a whole range of rows at once > (unlike a > > > scanner, which retrieves a range of rows one at a time)? > > > > > > > > > > > > On Apr 21, 2008, at 2:32 AM, Edward J. Yoon wrote: > > > > > > > > > > I think hbase need to make a TableResult and getSubTable() by range. > > > > > > > > -- > > > > B. Regards, > > > > Edward J. Yoon > > > > > > > > > > > > > > > > > > > > > > > > > -- > > B. Regards, > > Edward J. Yoon > > > > -- B. Regards, Edward J. Yoon
