[jira] [Updated] (IGNITE-14945) IndexQuery should use inline IO for internal filtering.

["Maksim Timonin (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-14945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maksim Timonin updated IGNITE-14945:
------------------------------------
    Description: 
For comparison of index keys it's required:
 # to init cache data row
 # access fields with BinaryObject API

So, it's possible to use inline IO for filtering. It can help:
 # speed up comparison (it's need to test whether Inline IO access significantly faster then BinaryObject API.
 # to avoid init cache data rows for filtered items (in case there are more filtered items).

> IndexQuery should use inline IO for internal filtering.
> -------------------------------------------------------
>
>                 Key: IGNITE-14945
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14945
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Maksim Timonin
>            Assignee: Maksim Timonin
>            Priority: Major
>              Labels: IEP-71
>
> For comparison of index keys it's required:
>  # to init cache data row
>  # access fields with BinaryObject API
> So, it's possible to use inline IO for filtering. It can help:
>  # speed up comparison (it's need to test whether Inline IO access significantly faster then BinaryObject API.
>  # to avoid init cache data rows for filtered items (in case there are more filtered items).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)