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 2021/12/16 09:40:00 UTC

[jira] [Updated] (IGNITE-16141) IndexQuery: consistency with query after IO filter

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

Maksim Timonin updated IGNITE-16141:
------------------------------------
    Summary: IndexQuery: consistency with query after IO filter  (was: IndexQuery: treeRange should return IndexRows with prefetched CacheDataRow)

> IndexQuery: consistency with query after IO filter
> --------------------------------------------------
>
>                 Key: IGNITE-16141
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16141
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Maksim Timonin
>            Assignee: Maksim Timonin
>            Priority: Major
>              Labels: IEP-71
>
> As we use InlineIO for internal filtering we should guarantee to return correct data row from this stage. Currently it returns GridCursor<IndexRow> but underlied IndexRow isn't initialized with CacheDataRow, and then it is affected by concurrent updates.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)