[IGNITE-14914] Support in() clause in IndexQuery.

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.14
• Labels: IEP-71 ise
• Release Note: Added support for IN criterion for IndexQuery: IndexQuery.setCriteria(in("A", Arrays.asList(1, 2 ,3))).
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Maksim Timonin
• Reporter: Maksim Timonin
• Created: 16/Jun/21 09:55
• Updated: 25/Aug/22 07:10
• Resolved: 17/Aug/22 11:25

Description

IndexQuery should support IN criterion:

IndexQuery.setCriteria(in("A", Arrays.asList(1, 2 ,3)));

1. IN criterion accepts collection of values to find. This collections is transformed to SortedSet(1, 2, 3) because IndexQuery provides to user sorted result.
2. When IN applies on first indexed field - IN(A0, A1) for index (A, B) - it converts to multiple eq operations are joint with OR operation: EQ(A0) or EQ(A1).
3. Other range criteria for other fields are applied to every such separate operation:
   IN(A0, A1) and GT(B) converts to (EQ(A0) and GT(B)) or (EQ(A1) and GT(B)).
4. When IN applies to non-leading indexed field - IN(B0, B1) for index (A, B) - it works like a filter for prepared range:
   GTE(A) and IN(B0, B1) converts to range [[A, B0]; [A, B1]] and every cache entry within this range is checked for being included to SortedSet(B0, B1).

Issue Links

• is related to: IGNITE-17543 Add IndexQuery support in Pyhon thin client
• is related to: IGNITE-17544 Add IndexQuery support in .NET thin client
• is related to: IGNITE-17545 Add IndexQuery support in С++ thin client
• links to: GitHub Pull Request #10195