Hi,
Talking to Lars we found a weird series of events that led to dying
task attempts during the bulk job they are running. See the attached
log. Region in question is:
raw_occurrence_record,28256992928,1290626317732.86e3cd5c5d0f22430debb36f1668d3fc
After a split the region is assigned to a new
Does hbase-dev still get forwarded? Did you see the below message?
-- Forwarded message --
From: Lars George lars.geo...@gmail.com
Date: Tue, Nov 23, 2010 at 4:25 PM
Subject: HRegion.RegionScanner.nextInternal()
To: hbase-...@hadoop.apache.org
Hi,
I am officially confused:
limit is for retrieving partial results of a row. Ie: give me a row
in chunks. Filters that want to operate on the entire row cannot be
used with this mode. i forget why it's in the loop but there was a
good reason at the time.
-ryan
On Thu, Nov 25, 2010 at 10:51 AM, Lars George
Mkay, I will look into it more for the latter. But for the limit this is still
confusing to me as limit == batch and that is in he client side the number of
rows. But not the number of columns. Does that mean if I had 100 columns and
set batch to 10 that it would only return 10 rows with 10
