[
https://issues.apache.org/jira/browse/CALCITE-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778940#comment-16778940
]
Vladimir Sitnikov commented on CALCITE-2817:
--------------------------------------------
Ok, it is just another case of CALCITE-2593.
rel#21:EnumerableValues.ENUMERABLE has multiple collations, thus simplify puts
it to \{{.ENUMERABLE.[]}} subset
So I would wait a bit for CALCITE-2593 resolution
> 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,
> values_vs_subset_placement.png
>
> Time Spent: 1h 20m
> 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)
