Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 6 Oct 2015 00:06:26 +0000 (UTC)
From: "Gopal V (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12902550.1444089733000.32044.1444089986720@Atlassian.JIRA>
In-Reply-To: <JIRA.12902550.1444089733000@Atlassian.JIRA>
References: <JIRA.12902550.1444089733000@Atlassian.JIRA>
 <JIRA.12902550.1444089733554@arcas>
Subject: [jira] [Resolved] (HIVE-12040) CBO: Use CBO, even for the 1 JOIN +
 GROUP BY case
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gopal V resolved HIVE-12040.
----------------------------
    Resolution: Duplicate

> CBO: Use CBO, even for the 1 JOIN + GROUP BY case
> -------------------------------------------------
>
>                 Key: HIVE-12040
>                 URL: https://issues.apache.org/jira/browse/HIVE-12040
>             Project: Hive
>          Issue Type: Improvement
>          Components: Logical Optimizer
>    Affects Versions: 1.3.0, 2.0.0
>            Reporter: Gopal V
>            Assignee: Gopal V
>             Fix For: 1.3.0, 2.0.0
>
>
> Hive CBO kicks in for a query only if a query has >1 joins, which is an archaic result of only re-ordering joins in the original impl.
> As more group-by & filter optimizers have been added, modify the CBO impl to kick in even if the query has a single JOIN.


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