Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <1980610274.1252981317530.JavaMail.jira@brutus>
Date: Mon, 14 Sep 2009 19:21:57 -0700 (PDT)
From: "Adam Kramer (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Created: (HIVE-832) Disallow OUTER JOIN with partition in
 WHERE clause in strict mode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Disallow OUTER JOIN with partition in WHERE clause in strict mode
-----------------------------------------------------------------

                 Key: HIVE-832
                 URL: https://issues.apache.org/jira/browse/HIVE-832
             Project: Hadoop Hive
          Issue Type: Wish
            Reporter: Adam Kramer


There is a wide-range poorly-understood issue in how WHERE and ON clauses work in the case of outer joins.

The WHERE filter is applied after the join. After an outer join, the INNER table (the left table in a RIGHT OUTER, or the left table in the LEFT OUTER) has all columns set to NULL for all rows. As a result, if ANY of them are cited in the WHERE clause, they will equal NULL. This almost always causes the join to effectively be an INNER join, even though the user typed the word O-U-T-E-R, probably for good reason.

In strict mode, we should not allow ANY COLUMNS from the inner table to appear in the WHERE clause.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.