[
https://issues.apache.org/jira/browse/CALCITE-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuzhao Chen updated CALCITE-2454:
---------------------------------
Description:
After CALCITE-2116, a RelNode will be reused based on digest, but now many
nodes's digests do not have type info, e.g. LogicalProject, this will affect
some rules when we wanna transform to a node with same digest and same type
(HepPlanner may pick out a RelNode with different type).
So, we should add type info just like VolcanoPlanner.
was:
After CALCITE-2116, a RelNode will be reused based on digest, but now many
nodes's digests do not have type info, e.g. LogicalProject, this will affect
some rules when we wann transform to a node with same digest but not same type
(or node).
So, we should add type info just like VolcanoPlanner.
> Fix bug in HepPlanner which occurred when two RelNodes have identical digest
> but different row-type
> ---------------------------------------------------------------------------------------------------
>
> Key: CALCITE-2454
> URL: https://issues.apache.org/jira/browse/CALCITE-2454
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.17.0
> Reporter: Yuzhao Chen
> Assignee: Julian Hyde
> Priority: Major
> Fix For: 1.18.0
>
>
> After CALCITE-2116, a RelNode will be reused based on digest, but now many
> nodes's digests do not have type info, e.g. LogicalProject, this will affect
> some rules when we wanna transform to a node with same digest and same type
> (HepPlanner may pick out a RelNode with different type).
> So, we should add type info just like VolcanoPlanner.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
