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

Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2021/12/07 09:45:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17454505#comment-17454505 ] 

Ignite TC Bot commented on IGNITE-14945:
----------------------------------------

{panel:title=Branch: [pull/9631/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9631/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=6307849&amp;buildTypeId=IgniteTests24Java8_RunAll]

> 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
>          Time Spent: 10m
>  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)