Given this index definition:
The following queries should be using this index and worked properly:
After several combined tests the only combination that worked was the
For the rest of the combinations the following error was raised:
The following issue was discussed with the N1QL team and the answer was to avoid using complex terms (IN, OR, etc.)on indexes to avoid indexing mismatch. In case of using, Query's IN clausule has to be exact to the index's one.
However, IN clause is allowed on CREATE INDEX sintax and doens't works as expected (manage a range of values).
On the other hand, equal operator works on single equal values, so query terms doesn't have to be exact to the Index's IN clause.
None of this limitations are documented on doc site and N1QL books.
After discussing this issue with the N1QL and the tiger team the following actions were detected:
- File this MB to fix the IN clause behaviour to expected
- Link to current customer CBSE
- File a DOC Issue to