You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Ashutosh Chauhan (JIRA)" <ji...@apache.org> on 2013/04/02 22:29:16 UTC

[jira] [Commented] (HIVE-3996) Correctly enforce the memory limit on the multi-table map-join

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

Ashutosh Chauhan commented on HIVE-3996:
----------------------------------------

[~vikram.dixit] Can you also update your RB entry with your latest patch?
                
> Correctly enforce the memory limit on the multi-table map-join
> --------------------------------------------------------------
>
>                 Key: HIVE-3996
>                 URL: https://issues.apache.org/jira/browse/HIVE-3996
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>    Affects Versions: 0.11.0
>            Reporter: Vikram Dixit K
>            Assignee: Vikram Dixit K
>         Attachments: HIVE-3996_2.patch, HIVE-3996_3.patch, HIVE-3996_4.patch, HIVE-3996_5.patch, HIVE-3996_6.patch, HIVE-3996.patch
>
>
> Currently with HIVE-3784, the joins are converted to map-joins based on checks of the table size against the config variable: hive.auto.convert.join.noconditionaltask.size. 
> However, the current implementation will also merge multiple mapjoin operators into a single task regardless of whether the sum of the table sizes will exceed the configured value.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira