You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Carl Steinbach (JIRA)" <ji...@apache.org> on 2010/07/26 08:32:51 UTC

[jira] Updated: (HIVE-1202) "Unknown exception : null" while join

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

Carl Steinbach updated HIVE-1202:
---------------------------------

    Fix Version/s:     (was: 0.4.1)
      Description: 
Hive throws "Unknown exception : null" with query:

select * from 
(
  select name from classes 
) a
  join classes b
where a.name > b.number

After tracing the code, I found this bug will occur with following
conditions:
1. It is join operation.
2. At least one of the source of join is physical table (right side in
above case).
3. With where condition and condition(s) of where clause must include
columns from both side of join (a.name and b.number in case)

  was:

Hive throws "Unknown exception : null" with query:

select * from 
(
  select name from classes 
) a
  join classes b
where a.name > b.number

After tracing the code, I found this bug will occur with following
conditions:
1. It is join operation.
2. At least one of the source of join is physical table (right side in
above case).
3. With where condition and condition(s) of where clause must include
columns from both side of join (a.name and b.number in case)


> "Unknown exception : null" while join
> -------------------------------------
>
>                 Key: HIVE-1202
>                 URL: https://issues.apache.org/jira/browse/HIVE-1202
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.4.1
>         Environment: hive-0.4.1
> hadoop 0.19.1
>            Reporter: Mafish
>         Attachments: HIVE-1202.branch-0.4.1.patch
>
>
> Hive throws "Unknown exception : null" with query:
> select * from 
> (
>   select name from classes 
> ) a
>   join classes b
> where a.name > b.number
> After tracing the code, I found this bug will occur with following
> conditions:
> 1. It is join operation.
> 2. At least one of the source of join is physical table (right side in
> above case).
> 3. With where condition and condition(s) of where clause must include
> columns from both side of join (a.name and b.number in case)

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