drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramana Inukonda Nagaraj (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-882) Join between hive table and parquet file fail
Date Tue, 03 Jun 2014 17:34:06 GMT

    [ https://issues.apache.org/jira/browse/DRILL-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016903#comment-14016903
] 

Ramana Inukonda Nagaraj commented on DRILL-882:
-----------------------------------------------

[~amansinha100] We do have a bug for parquet and json, Drill -881 . However that seems to
be a different issue. 

> Join between hive table and parquet file fail
> ---------------------------------------------
>
>                 Key: DRILL-882
>                 URL: https://issues.apache.org/jira/browse/DRILL-882
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Query Planning & Optimization
>            Reporter: Ramana Inukonda Nagaraj
>
> The following query fails with a cannot plan error
> select p.p_partkey 
>    from hive.part p, `tpch-multi/partsupp` ps 
>    where p.p_partkey = ps.ps_partkey 
>               and p.p_size = 41  
> order by p.p_partkey
> limit 20;
> The below queries work fine implying nothing is wrong with the source
> select p.p_partkey 
>    from hive.part p;
>    
> select ps.ps_partkey from `tpch-multi/partsupp` ps;
> The same query also works when both sides of join is from parquet or hive. Its only when
they are different that I get the below cannot plan error. 
> message: "Failure while parsing sql. < CannotPlanException:[ Node [rel#2666:Subset#26.PHYSICAL.SINGLETON([]).[]]
could not be implemented; planner state:



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

Mime
View raw message