https://issues.apache.org/jira/browse/HADOOP-2493
"stack" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Sounds like a bug Billy. hbase shouldn't be splitting rows. Please file
> a JIRA with how you brought on the condition and evidence of the split row
> (You're running TRUNK,
yes I was running trunk it was a few days back so I do not have a snap shot
of the regions but I can tell you how I produced it in Jira. will submit a
bug report.
Any suggestions on what the plans are if a section of a table get a lot of
rows for the same key say it get to be huge then what wou
Sounds like a bug Billy. hbase shouldn't be splitting rows. Please
file a JIRA with how you brought on the condition and evidence of the
split row (You're running TRUNK, right?).
Thanks,
St.Ack
Billy wrote:
Basically I have one row key that has a lot of parent:child cols in it the
parent is
Basically I have one row key that has a lot of parent:child cols in it the
parent is the same and the Childs are all different. I been testing the
splits part of the servers so set the region max size to 16MB so it would
split more often. when I can back after a log process had been running I had
l
Basically I have one row key that has a lot of parent:child cols in it the
parent is the same and the Childs are all different. I been testing the
splits part of the servers so set the region max size to 16MB so it would
split more often. when I can back after a log process had been running I ha
Billy wrote:
Hbase does split on a row key level so what's to happens if I have a row
that's larger then the max region size set in the conf?
My guess is that a row > configured region size would not be split.
I have one row that has been split into many smaller regions I just checking
if
