You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergi Vladykin (JIRA)" <ji...@apache.org> on 2015/09/14 15:30:46 UTC

[jira] [Resolved] (IGNITE-48) Ensure there is no race between quering data and swap/unswap.

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

Sergi Vladykin resolved IGNITE-48.
----------------------------------
    Resolution: Not A Problem
      Assignee: Vladimir Ozerov  (was: Semen Boikov)

> Ensure there is no race between quering data and swap/unswap.
> -------------------------------------------------------------
>
>                 Key: IGNITE-48
>                 URL: https://issues.apache.org/jira/browse/IGNITE-48
>             Project: Ignite
>          Issue Type: Task
>          Components: cache
>    Affects Versions: sprint-1
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>             Fix For: ignite-1.4
>
>
> Consider the following scenario:
> 1) Put a set of keys into cache so that they go to a SQL table "A".
> 2) Move some of these keys to swap.
> 3) Start quering table "A". Query will create snapshot of sorted index and will iterate it.
> 4) At the same update swapped keys so that they should go to another SQL table (e.g. change value type).
> The question is: what query engine will do when swapped key is met in index snapshot? If it will try to unswap it, then an error will be thrown (e.g. ClassCastException).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)