Initially to handle unnest with complex calls was introduced `ProjectComplexRexNodeCorrelateTransposeRule`. But this rule only matched `LogicalCorrelate -> Uncollect -> LogicalProject` pattern. So all other combinations, which have `LogicalCorrelate`, `Uncollect` and `LogicalProject` with rel nodes between `LogicalCorrelate` and `Uncollect` weren't handled.
The solution proposed in this PR is to make visitor based on `ProjectComplexRexNodeCorrelateTransposeRule` and apply it before applying rules, so all possible cases will be handled correctly. For details please see [DRILL-6703](https://issues.apache.org/jira/browse/DRILL-6703). [ Full content available at: https://github.com/apache/drill/pull/1441 ] This message was relayed via gitbox.apache.org for [email protected]
