hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-12503) GBY-Join transpose rule may go in infinite loop
Date Tue, 24 Nov 2015 15:53:11 GMT

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

Ashutosh Chauhan commented on HIVE-12503:
-----------------------------------------

Yup, currently we have kept this rule isolated from other rules, since we didn't want to have
plan space grow for Hep Planner since it has scalability issue. This patch doesn't change
that. Both before and after this patch, we are making a cost based decision for before and
after applying this particular transformation. It is just shifting logic from HepPlanner::applyTransformationResults()
to within the rule to avoid HePlanner::applyRules() go in infinite loop. When we test out
HepPlanner scalability properly we can enable this rule to be fired in rule collections so
that we can give a globally optimal plan.

> GBY-Join transpose rule may go in infinite loop
> -----------------------------------------------
>
>                 Key: HIVE-12503
>                 URL: https://issues.apache.org/jira/browse/HIVE-12503
>             Project: Hive
>          Issue Type: Bug
>          Components: CBO, Logical Optimizer
>    Affects Versions: 2.0.0
>            Reporter: Ashutosh Chauhan
>            Assignee: Ashutosh Chauhan
>         Attachments: HIVE-12503.1.patch, HIVE-12503.patch
>
>
> This happens when pushing aggregate is not found to be any cheaper. Can be reproduced
by running cbo_rp_auto_join1.q with flag turned on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message