Hi Namit/Siying,

 

Ok, even I agree with your analysis. Both the fixed and variable row size
evaluated wrongly here.

 

But what I was more interested in how critical is the change; like what if
hash aggregation map is not flushed, even if the number of existing entries
overshot the false entries stats calculated on basis of configured property
hive.map.aggr.map.percentmemory (whereas if it happens faithfully by the
code changes you did, it will trigger flush), any issues apart from out of
memory in child JVM or there is more to it, something else bad can happen?

 

If you can provide me the pointers to re-produce it's side effect, It will
be great.

 

-Mohit

 

****************************************************************************
***********
This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

  _____  

From: Mohit [mailto:mohitsi...@huawei.com] 
Sent: Tuesday, March 01, 2011 12:39 PM
To: 'siyin...@fb.com'
Subject: Regarding HIVE-1737

 

Hi Siying, 

 

Hope you doing great.

Well, I have one request regarding this defect, I'm not able to understand
and hence reproduce this issue.

May be you can help in that, I need to know what queries you ran.

 

-Mohit

 

****************************************************************************
***********
This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

 

Reply via email to