You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Sean Hsuan-Yi Chu (JIRA)" <ji...@apache.org> on 2015/02/26 17:07:04 UTC
[jira] [Commented] (DRILL-2238) Unsupported join on OR yields
rough CannotPlanException (vs. cleaner unsupported-feature message)
[ https://issues.apache.org/jira/browse/DRILL-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338618#comment-14338618 ]
Sean Hsuan-Yi Chu commented on DRILL-2238:
------------------------------------------
The query leads to cartesian join. see DRILL-1325
resolved in commit #: d72d6030e
> Unsupported join on OR yields rough CannotPlanException (vs. cleaner unsupported-feature message)
> --------------------------------------------------------------------------------------------------
>
> Key: DRILL-2238
> URL: https://issues.apache.org/jira/browse/DRILL-2238
> Project: Apache Drill
> Issue Type: Bug
> Components: Query Planning & Optimization, SQL Parser
> Reporter: Daniel Barclay (Drill)
> Assignee: Sean Hsuan-Yi Chu
> Priority: Minor
> Fix For: 0.9.0
>
>
> The unsupported combination of joining using a condition with an OR yields an internal CannotPlanException (with a dump of the plan):
> org.apache.drill.exec.rpc.RpcException: RelOptPlanner.CannotPlanException: Node [rel#4217:Subset#3.LOGICAL.ANY([]).[]] could not be implemented; planner state:
> Root: rel#4217:Subset#3.LOGICAL.ANY([]).[]
> Original rel:
> ...
> Eventually this should instead use some kind of unsupported-combination error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)