[
https://issues.apache.org/jira/browse/CALCITE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Antonucci updated CALCITE-740:
-------------------------------------
Description:
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.
was:
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.
> mongo-calcite produces incorrect results when query contains redundant
> 'where' clauses
> --------------------------------------------------------------------------------------
>
> 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
>
> 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)
