timoninmaxim commented on issue #10515: URL: https://github.com/apache/ignite/issues/10515#issuecomment-1419373203
Hi @DemonicTutor , > the order of the indexed fields defines the order how the clauses apply Yes, this is a correct. > I used CacheQueryExample to show the issue im facing Thanks for the reproducer, it is indeed a bug. Currently, a IN clause aborts checking other fields, if IN is not a first criterion. This is what I mean: 1. "eq" + "in" - works 2. "in" + "eq" - works 3. "eq" + "in" + "eq" - doesn't work (only "eq" + "in" part works as expected) I create a ticket for that, this behaviour will be fixed in 2.15. [1] https://issues.apache.org/jira/browse/IGNITE-18725 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
