You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/01/29 04:03:34 UTC

[jira] [Commented] (CALCITE-576) Make RelCollation trait and AbstractRelNode.getCollationList consistent

    [ https://issues.apache.org/jira/browse/CALCITE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296315#comment-14296315 ] 

Julian Hyde commented on CALCITE-576:
-------------------------------------

I'm solving these very issues as part of CALCITE-526. If you do a merge join of emp and dept both sorted on deptno, the output contain two deptno columns and will be sorted on both.

> Make RelCollation trait and AbstractRelNode.getCollationList consistent
> -----------------------------------------------------------------------
>
>                 Key: CALCITE-576
>                 URL: https://issues.apache.org/jira/browse/CALCITE-576
>             Project: Calcite
>          Issue Type: Bug
>    Affects Versions: 1.0.0-incubating
>            Reporter: Vladimir Sitnikov
>            Assignee: Julian Hyde
>
> Currently {{getCollationList}} is not consistent with {{RelCollation}} trait since a node can have only one collation trait, thus you cannot express the node that is sorted on multiple collations at the same time.
> We should either drop {{getCollationList}} in favour of {{getCollation}} or make collation trait support multiple "collation lists".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)