[CALCITE-4160] Add configuration to retain ORDER BY in sub-query

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.26.0
• Component/s: core
• Labels: pull-request-available
• Assignee: Jiatao Tao
• Reporter: Jiatao Tao
• Created: 06/Aug/20 06:44
• Updated: 16/Nov/21 11:38
• Resolved: 03/Sep/20 07:37

Description

Pre discussion see in 

https://issues.apache.org/jira/browse/CALCITE-2798

https://issues.apache.org/jira/browse/CALCITE-3664

IMO, we should at least provide a configuration about this. People use Calcite most for its optimizer, and this info users may care, How it executed is by the engine, but users should know this in the plan.
 

Issue Links

• is caused by: CALCITE-2798 Optimizer should remove ORDER BY in sub-query, provided it has no LIMIT or OFFSET
• is duplicated by: CALCITE-3664 Sort in subquery is lost when converting SqlNode to Relnode
• is related to: CALCITE-4886 When converting SQL to RelNode, SqlOrderBy is missing in sub-query that contains SqlSetOperator
• links to: GitHub Pull Request #2127