[
https://issues.apache.org/jira/browse/DRILL-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016286#comment-14016286
]
Aman Sinha commented on DRILL-882:
----------------------------------
Are you able to reproduce this with a join between a parquet file and json file
(that would indicate it is a general issue with cross data sources)....there
was an earlier bug DRILL-487 which also failed for cross data sources, although
the failure was at run-time due to SchemaChangeException, not during planning
time. Could you verify if the query in that bug still works ?
> 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)
