[CALCITE-740] Redundant WHERE clause causes wrong result in MongoDB adapter

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0-incubating
• Fix Version/s: 1.4.0-incubating
• Assignee: Julian Hyde
• Reporter: Robert Antonucci
• Created: 20/May/15 16:59
• Updated: 01/Sep/15 03:02
• Resolved: 13/Jun/15 01:09

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.