Re: Simple Pig query returns inaccurate result size for HBase tables of 1.8m+ rows

2011-01-25 Thread Mr. Lukas
1020576114013268896970538800 to 72576215356229636519498348368 (when interpreting those numbers as the arbitrary precision integer representation of the row key). Best regards, Lukas On Mon, Jan 24, 2011 at 10:07 AM, Mr. Lukas wrote: > Hi Dmitriy, > Sorry for the late reply, I was out of

Re: Simple Pig query returns inaccurate result size for HBase tables of 1.8m+ rows

2011-01-24 Thread Mr. Lukas
: > > This is quite odd because I do the same thing on a multi-million row table > and get multiple regions ... > You do have multiple regions, right? What happens if you only specify the > -loadKey parameter and none of the others? > > On Thu, Jan 20, 2011 at 8:24 AM, Mr. Lukas

Re: Simple Pig query returns inaccurate result size for HBase tables of 1.8m+ rows

2011-01-20 Thread Mr. Lukas
Hi pig users, I'm also using pig 0.8 together with HBase 0.20.6 and think, my problem is related to Ian's. When processing a table with millions of rows (stored in multiple), HBaseStorage won't scan the full table but only a few hundred records. The following minimal example reproduces my problem