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

Posted to issues@calcite.apache.org by "Vladimir Sitnikov (JIRA)" <ji...@apache.org> on 2019/02/13 19:29:00 UTC

[jira] [Resolved] (CALCITE-2817) Make CannotPlanException great

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

Vladimir Sitnikov resolved CALCITE-2817.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.19.0

Fixed in https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=d64f60cc513370cd409098f8ec997463329c1d6c

> Make CannotPlanException great
> ------------------------------
>
>                 Key: CALCITE-2817
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2817
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.18.0
>            Reporter: Vladimir Sitnikov
>            Assignee: Julian Hyde
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.19.0
>
>         Attachments: converters.png, running_rule.png, subsets.png
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> 1) Empty subsets are the typical offenders for CannotPlan, so identify them and print before printing the planner dump
> 2) Print Graphviz-compatible output as well so the output is easier to understand
> It would probably make sense to expose leafmost empty subsets via {{Set<RelSubset> CannotPlanExeption#getDeadSubsets()}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)