[
https://issues.apache.org/jira/browse/CALCITE-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Chen updated CALCITE-3649:
--------------------------------
Description:
If the AGG was transformed to PROJECT + AGG, the hints of AGG should be
propagated to the AGG node.
In current implementation, the hints would lost.
The perfect solution is to identify the replaced sub-tree, and for this tree,
we should check which node is the right one to attach hints. -But for this
patch, we only consider the new transformed node with pattern of PROJECT +
"node of same kind of original", this solves most of the cases.-
In current implementation, we try to match the first node of new relational
expression sub-tree. The first node satisfies if it:
* Does not have any existing hints on it
* Can apply the original hints
was:
If the AGG was transformed to PROJECT + AGG, the hints of AGG should be
propagated to the AGG node.
In current implementation, the hints would lost.
The perfect solution is to identify the replaced sub-tree, and for this tree,
we should check which node is the right one to attach hints. But for this
patch, we only consider the new transformed node with pattern of PROJECT +
"node of same kind of original", this solves most of the cases.
> Hints should be propagated correctly in planner rules if original node is
> transformed to different kind
> -------------------------------------------------------------------------------------------------------
>
> Key: CALCITE-3649
> URL: https://issues.apache.org/jira/browse/CALCITE-3649
> Project: Calcite
> Issue Type: Sub-task
> Components: core
> Affects Versions: 1.21.0
> Reporter: Danny Chen
> Assignee: Danny Chen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.22.0
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> If the AGG was transformed to PROJECT + AGG, the hints of AGG should be
> propagated to the AGG node.
> In current implementation, the hints would lost.
> The perfect solution is to identify the replaced sub-tree, and for this tree,
> we should check which node is the right one to attach hints. -But for this
> patch, we only consider the new transformed node with pattern of PROJECT +
> "node of same kind of original", this solves most of the cases.-
> In current implementation, we try to match the first node of new relational
> expression sub-tree. The first node satisfies if it:
> * Does not have any existing hints on it
> * Can apply the original hints
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
