You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2018/06/23 20:24:00 UTC

[jira] [Commented] (CALCITE-2370) Fix failing mongo IT tests when explicit order was not specified

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

Julian Hyde commented on CALCITE-2370:
--------------------------------------

[~vvysotskyi] in my opinion, you should not update the jira case description to say “fix ...”. Leave it so that it describes the problem. The commit message should be the same as the jira case. When the commit message describes a problem, everyone will easily realize that the purpose of the change is to fix the problem. 

> Fix failing mongo IT tests when explicit order was not specified
> ----------------------------------------------------------------
>
>                 Key: CALCITE-2370
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2370
>             Project: Calcite
>          Issue Type: Bug
>          Components: mongodb
>            Reporter: Andrei Sereda
>            Assignee: Julian Hyde
>            Priority: Major
>             Fix For: 1.17.0
>
>
> By default mongo does not guarantee return order of documents unless explicit sort is specified.
> Changed test to sort states by name to have more deterministic result



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)