[
https://issues.apache.org/jira/browse/CALCITE-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292461#comment-17292461
]
Julian Hyde commented on CALCITE-4514:
--------------------------------------
[~botong], Thanks for the update. I'll take it from here, test and merge your
change. (There are a couple of minor things that I will fix: while it's a good
idea to remove the {{VolcanoPlanner planner}} argument, that constitutes an API
change, so we shouldn't do it; and the test should use assertThat rather than
assert.)
> [CALCITE-4514] Fine tune the merge order of two RelSets
> -------------------------------------------------------
>
> Key: CALCITE-4514
> URL: https://issues.apache.org/jira/browse/CALCITE-4514
> Project: Calcite
> Issue Type: Improvement
> Reporter: Botong Huang
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When merging two relsets, we have two preferences:
> 1. Merge parent relset into child relset
> 2. Merge newer relset into older relset
> Currently, when the two relsets are parent set of each other, we randomly
> pick a merge order without checking the second condition above. For
> performance reasons, we should, to avoid unnecessary churn.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
