[
https://issues.apache.org/jira/browse/CALCITE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937124#comment-15937124
]
Gian Merlino commented on CALCITE-1719:
---------------------------------------
Got it, that makes sense. This rule should be fine then, since it's not
assuming anything about the order of rows coming out of the inner Sort. It just
merges two layers of limit/offset.
I get the thing about the style. Fwiw, in Druid we have an IntelliJ config and
a checkstyle verifier as well. Neither one catches everything we care about,
but together they catch most things. Contributors don't need to use IntelliJ,
but the ones that do will get fewer style changes requested in code review.
> SortCollapseRule for collapsing nested sorts
> --------------------------------------------
>
> Key: CALCITE-1719
> URL: https://issues.apache.org/jira/browse/CALCITE-1719
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Gian Merlino
> Assignee: Julian Hyde
>
> Useful for subqueries like {{SELECT * FROM (...) LIMIT X}}, where the inner
> query might have an order by or limit.
> Patch in https://github.com/apache/calcite/pull/410.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
