[IGNITE-14945] IndexQuery should use inline IO for internal filtering.

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Resolved
• Fix Version/s: 2.13
• Labels: IEP-71
• Release Note: Improved IndexQuery for index rows filtering
• Ignite Flags: Release Notes Required
• Assignee: Maksim Timonin
• Reporter: Maksim Timonin
• Created: 18/Jun/21 12:33
• Updated: 01/Apr/22 07:59
• Resolved: 14/Dec/21 14:22

Description

For comparison of index keys it's required:

1. to init cache data row
2. access fields with BinaryObject API

So, it's possible to use inline IO for filtering. It can help:

1. speed up comparison (Inline IO access is faster than BinaryObject API).
2. to avoid init cache data rows for filtered items (in case there are more filtered items).

Issue Links

• is related to: IGNITE-16123 Broken LazyOnDmlTest for MVCC due to incorrect check in InlineFilterClosure
• links to: GitHub Pull Request #9631