[
https://issues.apache.org/jira/browse/CALCITE-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190484#comment-17190484
]
Danny Chen commented on CALCITE-4160:
-------------------------------------
Fixed in
[734a7ac|https://github.com/apache/calcite/commit/734a7acd4cef2e3c2ef529844cf34e9fa8173aea]
and
[42785e4|https://github.com/apache/calcite/commit/42785e4f63f5d841655a8fdc4f9b81b310e33841],
thanks for the PR, [~Aron.tao] !
> Add configuration to retain ORDER BY in sub-query
> -------------------------------------------------
>
> Key: CALCITE-4160
> URL: https://issues.apache.org/jira/browse/CALCITE-4160
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Jiatao Tao
> Assignee: Jiatao Tao
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.25.0
>
> Attachments: image-2020-08-07-10-48-59-599.png,
> image-2020-08-07-10-50-22-351.png
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> 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.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
