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 2015/06/08 21:05:00 UTC

[jira] [Updated] (CALCITE-740) Redundant WHERE clause causes wrong result in MongoDB adapter

     [ https://issues.apache.org/jira/browse/CALCITE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde updated CALCITE-740:
--------------------------------
    Summary: Redundant WHERE clause causes wrong result in MongoDB adapter  (was: mongo-calcite produces incorrect results when query contains redundant 'where' clauses)

> Redundant WHERE clause causes wrong result in MongoDB adapter
> -------------------------------------------------------------
>
>                 Key: CALCITE-740
>                 URL: https://issues.apache.org/jira/browse/CALCITE-740
>             Project: Calcite
>          Issue Type: Bug
>    Affects Versions: 1.2.0-incubating
>            Reporter: Robert Antonucci
>            Assignee: Julian Hyde
>             Fix For: next
>
>
> Running a query with the 'where' clause:
>      {{where (pop > 8000 and pop > 9000)}}
> does not produce the same result as:
>      {{where pop > 9000}}
> instead it produces the same result as:
>      {{where pop > 8000}}
> This was run using calcite-mongo's zips collection.
> The interpreter appears to treat the 'and' as an 'or'.  This despite the fact that queries like:
>      {{where (pop > 8000 and pop < 9000)}}
> work as you would expect.
> Tried this on other data stores and did not see the same problem.  Just calcite-mongo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)