You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Maksim Timonin (Jira)" <ji...@apache.org> on 2022/04/01 08:00:00 UTC

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

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

Maksim Timonin updated IGNITE-14945:
------------------------------------
    Ignite Flags: Release Notes Required  (was: Docs Required,Release Notes Required)

> 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
>             Fix For: 2.13
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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 (Inline IO access is faster than 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.20.1#820001)