[CALCITE-576] Make RelCollation trait and AbstractRelNode.getCollationList consistent

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0-incubating
• Fix Version/s: 1.1.0-incubating
• Assignee: Julian Hyde
• Reporter: Vladimir Sitnikov
• Created: 28/Jan/15 08:18
• Updated: 23/Mar/15 08:08
• Resolved: 08/Feb/15 17:32

Description

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".

Issue Links

• depends upon: CALCITE-526 Add EnumerableMergeJoin, which exploits sorted inputs