Re: Integer key range scan

2008-12-16 Thread Clint Morgan
--- > > From: clint@gmail.com [mailto:clint@gmail.com] On Behalf Of > > Clint Morgan > > Sent: Tuesday, December 16, 2008 2:41 PM > > To: hbase-user@hadoop.apache.org > > Subject: Re: Integer key range scan > > > > Actually, thats not the case: &g

RE: Integer key range scan

2008-12-16 Thread Jonathan Gray
December 16, 2008 2:41 PM > To: hbase-user@hadoop.apache.org > Subject: Re: Integer key range scan > > Actually, thats not the case: > > @Test > public void test() { > > Integer lastInt = 0; > byte[] lastBytes = null; > for (int

Re: Integer key range scan

2008-12-16 Thread Clint Morgan
com] On Behalf Of > > Clint Morgan > > Sent: Tuesday, December 16, 2008 2:13 PM > > To: hbase-user@hadoop.apache.org > > Subject: Re: Integer key range scan > > > > Does intToBytes preserve ordering? IE is the leicographic ordering of > > the &g

Re: Integer key range scan

2008-12-16 Thread Dave Latham
ay, December 16, 2008 2:13 PM > > To: hbase-user@hadoop.apache.org > > Subject: Re: Integer key range scan > > > > Does intToBytes preserve ordering? IE is the leicographic ordering of > > the > > resulting byte [] the same as the ordering of the original ints? >

RE: Integer key range scan

2008-12-16 Thread Jonathan Gray
Clint Morgan > Sent: Tuesday, December 16, 2008 2:13 PM > To: hbase-user@hadoop.apache.org > Subject: Re: Integer key range scan > > Does intToBytes preserve ordering? IE is the leicographic ordering of > the > resulting byte [] the same as the ordering of the original ints? >

Re: Integer key range scan

2008-12-16 Thread Clint Morgan
ty in web ui/shell it's far > more efficient. > > JG > > > -Original Message- > > From: edw...@udanax.org [mailto:edw...@udanax.org] On Behalf Of Edward > > J. Yoon > > Sent: Tuesday, December 16, 2008 9:39 AM > > To: hbase-user@hadoop.apache.org

RE: Integer key range scan

2008-12-16 Thread Jonathan Gray
ngs a bit less pretty in web ui/shell it's far more efficient. JG > -Original Message- > From: edw...@udanax.org [mailto:edw...@udanax.org] On Behalf Of Edward > J. Yoon > Sent: Tuesday, December 16, 2008 9:39 AM > To: hbase-user@hadoop.apache.org > Subject: Re: In

Re: Integer key range scan

2008-12-16 Thread Edward J. Yoon
Oh Yes, Thanks for tip J-D. On Wed, Dec 17, 2008 at 2:27 AM, Jean-Daniel Cryans wrote: > Yes, then you would scan with startrow = 35 and stoprow = 000236 > if this is really what you want to do. > > J-D > > On Tue, Dec 16, 2008 at 12:25 PM, Edward J. Yoon wrote: > >> Like this? 00

Re: Integer key range scan

2008-12-16 Thread Jean-Daniel Cryans
Yes, then you would scan with startrow = 35 and stoprow = 000236 if this is really what you want to do. J-D On Tue, Dec 16, 2008 at 12:25 PM, Edward J. Yoon wrote: > Like this? 35 ~ 000235 > > On Wed, Dec 17, 2008 at 2:21 AM, Jean-Daniel Cryans > wrote: > > You can left

Re: Integer key range scan

2008-12-16 Thread Edward J. Yoon
Like this? 35 ~ 000235 On Wed, Dec 17, 2008 at 2:21 AM, Jean-Daniel Cryans wrote: > You can left pad with zeroes then use the scanning facility for faster > retrieval. > > J-D > > On Tue, Dec 16, 2008 at 12:18 PM, Edward J. Yoon wrote: > >> I would use integer key and extract data fro

Re: Integer key range scan

2008-12-16 Thread Jean-Daniel Cryans
You can left pad with zeroes then use the scanning facility for faster retrieval. J-D On Tue, Dec 16, 2008 at 12:18 PM, Edward J. Yoon wrote: > I would use integer key and extract data from range scans. But, hbase > row/column is alphabetically sorted. > > So, I wrote like below: > > for (int i

Integer key range scan

2008-12-16 Thread Edward J. Yoon
I would use integer key and extract data from range scans. But, hbase row/column is alphabetically sorted. So, I wrote like below: for (int i = 35; i <= 235; i++) { table.getRow(i, columns[]); } It seems, causes too many requests over hbase. Any suggestion? -- Best Regards, Edward J. Yoon @