[
https://issues.apache.org/jira/browse/CALCITE-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haisheng Yuan resolved CALCITE-4007.
------------------------------------
Fix Version/s: 1.24.0
Resolution: Fixed
Fixed in
[https://github.com/apache/calcite/commit/dcc76cede53c7971bc9c3755d9261e766aa63b66].
> MergeJoin collation check should not be limited to join key's order
> -------------------------------------------------------------------
>
> Key: CALCITE-4007
> URL: https://issues.apache.org/jira/browse/CALCITE-4007
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Haisheng Yuan
> Priority: Minor
> Fix For: 1.24.0
>
>
> Given MergeJoin on foo.a=bar.a and foo.b=bar.b,
> The collation check on MergeJoin always require it is sorted by (a,b), but
> after 1.23.0 calcite can generate MergeJoin on collation of (b,a), or even
> (a,b,c), (b,a,c), which are all legit. We should relax the check condition.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
