You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Zoltan Haindrich (JIRA)" <ji...@apache.org> on 2018/02/27 17:01:00 UTC

[jira] [Commented] (HIVE-18813) Fix mapjoin_hook

    [ https://issues.apache.org/jira/browse/HIVE-18813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16378943#comment-16378943 ] 

Zoltan Haindrich commented on HIVE-18813:
-----------------------------------------

[~ashutoshc] could you take a look?

> Fix mapjoin_hook
> ----------------
>
>                 Key: HIVE-18813
>                 URL: https://issues.apache.org/jira/browse/HIVE-18813
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>            Priority: Major
>         Attachments: HIVE-18813.01.patch
>
>
> this test fails from time to time...it seems like it has some memory issues
> the reason that the exception is changing; is because the test tries to tweak to cause an "exhausted memory" state - and because HIVE-13567 have enable autogather which adds an UDAF to aggregate; the previous setting doesn't apply anymore; because there will be a groupby which is controlled by another property
> hive.mapjoin.localtask.max.memory.usage is set 
> but not hive.mapjoin.followby.gby.localtask.max.memory.usage



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)