hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kramer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-832) Disallow OUTER JOIN with partition in WHERE clause in strict mode
Date Tue, 15 Sep 2009 18:54:57 GMT

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

Adam Kramer commented on HIVE-832:

I think if that's going on (seems like a valid use case upon reflection, but kind of a hack),
requiring safe mode = off and/or throwing a warning is reasonable.

> 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.

View raw message