Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 29 Oct 2014 18:25:34 +0000 (UTC)
From: "Ashutosh Chauhan (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12750930.1414453430000.365062.1414607134506@Atlassian.JIRA>
In-Reply-To: <JIRA.12750930.1414453430000@Atlassian.JIRA>
References: <JIRA.12750930.1414453430000@Atlassian.JIRA>
 <JIRA.12750930.1414453430784@arcas>
Subject: [jira] [Updated] (HIVE-8625) Some union queries result in plans
 with many unions with CBO on
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Ashutosh Chauhan updated HIVE-8625:
-----------------------------------
    Fix Version/s:     (was: 0.15.0)
                   0.14.0

> Some union queries result in plans with many unions with CBO on
> ---------------------------------------------------------------
>
>                 Key: HIVE-8625
>                 URL: https://issues.apache.org/jira/browse/HIVE-8625
>             Project: Hive
>          Issue Type: Bug
>          Components: CBO
>    Affects Versions: 0.14.0
>            Reporter: Jes=C3=BAs Camacho Rodr=C3=ADguez
>            Priority: Minor
>             Fix For: 0.14.0
>
>         Attachments: HIVE-8625.patch
>
>
> For some queries e.g. union9, union16, we are getting plans with many bin=
ary unions when CBO is on. The reason is that an identity select operator i=
s introduced after each union by the CBO; thus, the method that was merging=
 the unions when the translation of the AST into a logical plan was being d=
one is not executed, as it does not detect there is another union operator.=
=20
> With the fix in the patch attached, the method will merge the two unions =
if (1) one is the child of the other one, or (2) if one is a descendant of =
the other one and there is an identity select operator between them.


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