You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by "Vladimir Sitnikov (JIRA)" <ji...@apache.org> on 2014/06/29 19:38:24 UTC

[jira] [Commented] (OPTIQ-316) SqlRun: Match output regardless of order if ORDER BY not present

    [ https://issues.apache.org/jira/browse/OPTIQ-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047183#comment-14047183 ] 

Vladimir Sitnikov commented on OPTIQ-316:
-----------------------------------------

Any chance we use some more standard syntax for SqlRun?

As I implemented window aggregates, I did try adding SqlRun tests, but I failed. I even failed to un-comment already existing tests.
The current syntax itself is obscure, and it is hard to debug.

> SqlRun: Match output regardless of order if ORDER BY not present
> ----------------------------------------------------------------
>
>                 Key: OPTIQ-316
>                 URL: https://issues.apache.org/jira/browse/OPTIQ-316
>             Project: optiq
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>
> If ORDER BY is not present, a compliant implementation may return rows in any order. SqlRun should detect this, output the rows in the original order, not the actual order.
> This feature makes it much easier to handle unsorted data. The previous workaround, adding an ORDER BY clause, may trigger a different execution path and mask bugs. And it was common to forget an ORDER BY and have to go back to add the ORDER BY and correct the data some weeks later.



--
This message was sent by Atlassian JIRA
(v6.2#6252)