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

Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2022/12/02 13:07:00 UTC

[jira] [Created] (IGNITE-18322) Define scan contract SortedIndexStorage

Kirill Tkalenko created IGNITE-18322:
----------------------------------------

             Summary: Define scan contract SortedIndexStorage
                 Key: IGNITE-18322
                 URL: https://issues.apache.org/jira/browse/IGNITE-18322
             Project: Ignite
          Issue Type: Improvement
            Reporter: Kirill Tkalenko
             Fix For: 3.0.0-beta2


We need to define a contract for *org.apache.ignite.internal.storage.index.SortedIndexStorage#scan*, specifically how should we deal with concurrent storage updates?

For rocksDB, we have snapshot isolation defined, i.e. we will not see any parallel storage updates.

For BplusTree(PageMemory), we get the values in batches, we will take parallel storage updates only when the next batch is received.

It would be nice to define the general behavior of the scan, since we cannot implement snapshot isolation for a BplusTree(PageMemory), we can either leave it as it is or always get up-to-date rows.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)