[CALCITE-816] Represent sub-query as a RexNode

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.6.0
• Assignee: Julian Hyde
• Reporter: Julian Hyde
• Created: 25/Jul/15 05:01
• Updated: 06/Jul/17 23:17
• Resolved: 11/Jan/16 04:56

Description

Represent IN, NOT IN, EXISTS and scalar sub-queries as RexSubQuery extends RexNode. Then we can write a planner rule that expands sub-queries.

Issue Links

• breaks: CALCITE-1055 SubQueryRemoveRule should create Correlate, not Join, for correlated sub-queries
• is depended upon by: CALCITE-1799 "OR ... IN" sub-query conversion is wrong
• is related to: CALCITE-1799 "OR ... IN" sub-query conversion is wrong
• relates to: CALCITE-838 Optimize "join to most recent" queries
• relates to: CALCITE-863 AssertionError while translating query with UNNEST and having two correlation conditions
• relates to: CALCITE-709 LIMIT inside scalar sub-query
• relates to: CALCITE-551 Sub-query inside aggregate function
• relates to: CALCITE-842 Decorrelator gets field offsets confused if fields have been trimmed
• relates to: CALCITE-864 Correlation variable has incorrect row type if it is populated by right side of a Join