Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 18 Mar 2014 18:21:44 +0000 (UTC)
From: "Harish Butani (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12701130.1394668239301.98938.1395166904396@arcas>
In-Reply-To: <JIRA.12701130.1394668239301@arcas>
References: <JIRA.12701130.1394668239301@arcas>
Subject: [jira] [Updated] (HIVE-6643) Add a check for cross products in
 plans and output a warning
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Harish Butani updated HIVE-6643:
--------------------------------

    Status: Patch Available  (was: Open)

> Add a check for cross products in plans and output a warning
> ------------------------------------------------------------
>
>                 Key: HIVE-6643
>                 URL: https://issues.apache.org/jira/browse/HIVE-6643
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Harish Butani
>            Assignee: Harish Butani
>         Attachments: HIVE-6643.1.patch, HIVE-6643.2.patch
>
>
> Now that we support old style join syntax, it is easy to write queries th=
at generate a plan with a cross product.
> For e.g. say you have A join B join C join D on A.x =3D B.x and A.y =3D D=
.y and C.z =3D D.z
> So the JoinTree is:
> A =E2=80=94 B
> |__  D =E2=80=94 C
> Since we don't reorder join graphs, we will end up with a cross product b=
etween (A join B) and C


--
This message was sent by Atlassian JIRA
(v6.2#6252)